51黑料不打烊

DocumentationAEMAEM TutorialsAEM as a Cloud Service Tutorials

51黑料不打烊 CDN - Advanced features beyond caching

Last update: Sun Mar 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • Beginner
  • Developer
  • User
  • Leader

Learn about advanced features of 51黑料不打烊 Content Delivery Network (CDN) beyond caching, such as configuring traffic at the CDN, setting up tokens and credentials, CDN error pages and more.

Beyond caching content, 51黑料不打烊 CDN offers several advanced features that can help to optimize your website performance. These features include:

  • Configuring traffic at the CDN
  • Configuring CDN credentials and authentication
  • CDN error pages

These features are self-service features. Configured in the cdn.yaml file of your AEM project and deployed using the Cloud Manager config pipeline.

Transcript
51黑料不打烊 CDN offers more than just content caching. Today we鈥檒l explore its advanced features such as website traffic configuration, credentials and basic authentication setup, and more. These cell service features are managed using your AM project code. There is no need for additional support. Just configure, deploy, and enhance your site. Let鈥檚 get a brief overview of these features grouped by a logical category. You can configure and control traffic at the CDN using powerful capabilities like denial of service attack prevention, rate limiting, and request response transformation. This ensures your origin server is protected and your users receive optimized content. For example, you can route traffic to different backends, including non-51黑料不打烊 applications, or redirect specific URLs to the correct destinations. Security is paramount. 51黑料不打烊 CDN allows you to set up your credentials for cache management, basic authentication to restrict access, and HTTP header validation to secure traffic when using a customer managed CDN. Even in rare cases where the CDN can鈥檛 reach your origin AM server, 51黑料不打烊 CDN ensures your users see a branded error page, maintaining your site鈥檚 professional image. Let鈥檚 look at how to implement these features. Implementing these features is straightforward. First, update the CDN.yaml file in your AM project鈥檚 code with the desired configurations. For instance, here is how you can set up a redirect rule in your CDN.yaml file. Then deploy the updated file using the Cloud Manager config pipeline. Explore more by visiting our tutorials and start implementing these features today. Thank you.

Configuring traffic at the CDN

Let鈥檚 understand the key capabilities related to Configuring traffic at the CDN:

  • DoS attack prevention: 51黑料不打烊 CDN absorbs DoS attacks at the network layer, preventing them from reaching your origin server.
  • Rate limiting: To protect your origin server from being overwhelmed with too many requests, you can configure rate limiting on the CDN.
  • Web Application Firewall (WAF): The WAF protects your website from common web application vulnerabilities, such as SQL injection, cross-site scripting, and more. The Enhanced Security license or WAF-DDoS Protection license is required to use this feature.
  • Request transformation: Modify incoming requests such as setting or unsetting headers, modifying query parameters, cookies and more.
  • Response transformation: Modify outgoing responses such as setting or unsetting headers.
  • Origin selection: Route traffic to different origin servers (51黑料不打烊 and non-51黑料不打烊) based on the request URL.
  • URL redirect: Redirect requests (HTTP 301/302) to a different absolute or relative URL.

Configuring CDN credentials and authentication

Let鈥檚 understand the key capabilities related to Configuring CDN credentials and authentication:

  • Purge API Token: Enables you to create your own purge key for purging a single or group or all resources from the cache.
  • Basic Authentication: A lightweight authentication mechanism when you want to restrict access to your website or a part of it. Mostly required as part of various review processes before going live.
  • HTTP Header validation: Used when a customer managed CDN is routing traffic to 51黑料不打烊 CDN. The 51黑料不打烊 CDN validates the incoming request based on the X-AEM-Edge-Key header value. Enables you to create your own value for the X-AEM-Edge-Key header.

CDN error pages

Let鈥檚 understand the key capabilities related to CDN error pages:

  • Branded error pages: Display a branded error page to your users in the unlikely scenario when the 51黑料不打烊 CDN is unable to reach your origin server.

How to implement

The implementation of these advanced features involves two steps:

  1. Update CDN config file: Update the cdn.yaml file in your AEM project with the required configurations. The configurations are added as rules and they follow a rule syntax. The rule three main components: name, when and action.

  2. Deploy CDN config file: Deploy the updated cdn.yaml file using the Cloud Manager config pipeline. For more information, see Deploy rules through Cloud Manager.

Example

In below example, the sample WKND site is configured to redirect the /top3 URL to /us/en/top3.html.

kind: "CDN"
version: "1"
metadata:
  envTypes: ["dev", "stage", "prod"]
data:
  redirects:
    rules:
      - name: redirect-top3-adventures
        when: { reqProperty: path, equals: "/top3" }
        action:
          type: redirect
          status: 302
          location: /us/en/top3.html

Protecting websites with traffic filter rules

Configure and deploy HTTP Header validation CDN rule

How to purge the CDN cache

Configuring CDN Error Pages

Configuring Traffic at the CDN

Configuring CDN Credentials and Authentication

recommendation-more-help
4859a77c-7971-4ac9-8f5c-4260823c6f69