Skip to content

Default Cache Behavior

Cache behavior allows you to configure various ACDN features for specific URL path patterns of files on your website.

​

Path Pattern: Default is all files
Auto-compress objects: Default is Yes

Protocol Policy

Choose the protocol policy you want viewers to use when accessing content from ACDN edge sites.

  • ​​HTTP and HTTPS​​: Viewers can use both protocols.
  • ​​Redirect HTTP to HTTPS​​: Viewers can use both protocols, but HTTP requests will automatically redirect to HTTPS requests.
  • ​​HTTPS Only​​: Viewers can only access your content if they use HTTPS.

Allowed HTTP Methods

Specify the HTTP methods you want ACDN to process and forward to the origin.

  • ​​GET, HEAD​​: You can only use ACDN to fetch objects from your origin or retrieve object headers.
  • ​​GET, HEAD, OPTIONS​​: You can only use ACDN to fetch objects, retrieve headers, or get a list of options supported by your origin server.
  • ​​GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE​​: You can use ACDN to fetch, add, update, and delete objects, as well as retrieve headers. Additionally, you can perform other POST operations, such as submitting data from web forms.

Cache Policy

With managed cache policies, you don’t need to write or maintain your own caching policies.

Amplify

This policy is suitable for origins serving as AWS Amplify web applications.

This policy includes the following settings:

  • Minimum TTL: 2 seconds
  • Maximum TTL: 600 seconds (10 minutes)
  • Default TTL: 2 seconds
  • Headers included in cache key:
  • Authorization
  • CloudFront-Viewer-Country
  • Host
    Also includes the standardized Accept-Encoding header.
  • Cookies included in cache key: All cookies.
  • Query strings included in cache key: All query strings.
  • Cache compressed objects setting: Enabled.

CachingDisabled

This policy disables caching. It is useful for dynamic content and non-cacheable requests.

This policy includes the following settings:

  • Minimum TTL: 0 seconds
  • Maximum TTL: 0 seconds
  • Default TTL: 0 seconds
  • Headers included in cache key: None
  • Cookies included in cache key: None
  • Query strings included in cache key: None
  • Cache compressed objects setting: Disabled

CachingOptimized

This policy aims to improve cache efficiency by minimizing the values ACDN includes in the cache key. ACDN does not include any query strings or cookies in the cache key and only includes the standardized Accept-Encoding header.

This policy includes the following settings:

  • Minimum TTL: 1 second
  • Maximum TTL: 31536000 seconds (365 days)
  • Default TTL: 86400 seconds (24 hours)
  • Headers included in cache key: No explicitly included headers. Includes the standardized Accept-Encoding header.
  • Cookies included in cache key: None
  • Query strings included in cache key: None
  • Cache compressed objects setting: Enabled

CachingOptimizedForUncompressedObjects

This policy aims to improve cache efficiency by minimizing the values included in the cache key. It excludes query strings, headers, and cookies. This policy is identical to the previous one but disables the cache compressed objects setting.

This policy includes the following settings:

  • Minimum TTL: 1 second
  • Maximum TTL: 31536000 seconds (365 days)
  • Default TTL: 86400 seconds (24 hours)
  • Headers included in cache key: None
  • Cookies included in cache key: None
  • Query strings included in cache key: None
  • Cache compressed objects setting: Disabled

Elemental-MediaPackage

This policy is designed for origins serving as AWS Elemental MediaPackage endpoints.

This policy includes the following settings:

  • Minimum TTL: 0 seconds
  • Maximum TTL: 31536000 seconds (365 days)
  • Default TTL: 86400 seconds (24 hours)
  • Headers included in cache key:
  • Origin
    Also includes the standardized Accept-Encoding header.
  • Cookies included in cache key: None
  • Query strings included in cache key:
  • aws.manifestfilter
  • start
  • end
  • m

Origin Request Policy

With managed origin request policies, you don’t need to write or maintain your own origin request policies.

Managed-AllViewer

This policy includes all values (headers, cookies, and query strings) from the viewer request.

This policy includes the following settings:

  • Headers included in origin request: All headers from the viewer request
  • Cookies included in origin request: All
  • Query strings included in origin request: All

Managed-CORS-CustomOrigin

This policy includes headers that enable Cross-Origin Resource Sharing (CORS) requests when the origin is a custom origin.

This policy includes the following settings:

  • Headers included in origin request:
  • Origin
  • Cookies included in origin request: None
  • Query strings included in origin request: None

Managed-CORS-S3Origin

This policy includes headers that enable Cross-Origin Resource Sharing (CORS) requests when the origin is an Amazon S3 bucket.

This policy includes the following settings:

  • Headers included in origin request:
  • Origin
  • Access-Control-Request-Headers
  • Access-Control-Request-Method
  • Cookies included in origin request: None
  • Query strings included in origin request: None

Managed-Elemental-MediaTailor-PersonalizedManifests

This policy is designed for origins serving as AWS Elemental MediaTailor endpoints.

This policy includes the following settings:

  • Headers included in origin request:
  • Origin
  • Access-Control-Request-Headers
  • Access-Control-Request-Method
  • User-Agent
  • X-Forwarded-For
  • Cookies included in origin request: None
  • Query strings included in origin request: All

Managed-UserAgentRefererHeaders

This policy includes only the User-Agent and Referer headers. It does not include any query strings or cookies.

This policy includes the following settings:

  • Headers included in origin request:
  • User-Agent
  • Referer
  • Cookies included in origin request: None
  • Query strings included in origin request: None