![]() The process of making your application or web site perform better, however, is not always clear. If you have multiple instances of the Caching behavior in your property, for example, you configure another Caching behavior in a nested rule, the last occurring instance of the behavior takes precedence.We all know that the performance of applications and web sites is a critical factor in their success. Note also that settings from certain requests - for example, cache instructions sent with ESI requests override origin headers and configuration settings, other than no-store or bypass-cache. To override these options, you must turn them off, for example, by using Edge-Control response headers. ![]() The No store and Bypass cache options can't be overridden by any other caching settings. With Enhanced RFC support enabled,the settings that determine when cached objects expire include, in order of precedence: no-cache, s-maxage(with Honor s-maxage enabled), max-age(with Honor max-age enabled), pre-check, and the Default maxage setting. If the Expires header is present, it takes precedence over the Default maxage setting. With Enhanced RFC support disabled, the settings that determine when cached objects expire include, in order of precedence: max-age, pre-check, and the Default maxage setting. The precedence is affected by the Enhanced RFC support in the following ways: When you select Honor origin Cache-Control or Honor origin Cache-Control and Expires as your caching option, origin caching headers take precedence over property configuration settings, and the Cache-Control header overrides the Expires header. Test your configuration in the staging environment to ensure that caching works as you expect. Turning on Enhanced RFC support for an existing property may change the way your traffic is cached. The directives are grouped by functionality. The directives adhere to RFC-standards, except for the no-transform one, which is disabled by default. You can enable Enhanced RFC support that lets you honor additional Cache-Control header directives from the origin. Default maxage is ignored if another honored directive that affects TTL is used by the origin. Set the Default maxage edge servers can use in case the relevant origin header is not found or is invalid. Edge servers can either serve the object only if it has been re-fetched or validated at the origin, or serve stale, which is useful when the origin is not available. If the must-revalidate or proxy-revalidate directives are not present in the Cache-Control header, in the Force revalidation of stale objects field, specify what to do when an object's caching life has expired. Select this option to configure content caching through honoring the Cache-Control and Expires response headers from the origin.įor Honor origin Cache-Control and Honor Cache-Control and Expires options, if the Cache-Control header contains the must-revalidate or proxy-revalidate directives, edge servers ignore the Force revalidation of stale objects setting and don't serve stale content unless validated with the origin server. Tiered Distribution for API Acceleration.Resource Optimizer Extended Compatibility.Protocol Downgrade (HTTPS Downgrade to Origin). ![]() Media Acceleration (QUIC Protocol) Opt-Out.Device Characterization - Forward in Header.Device Characterization - Define Cached Content.Content Characteristics - Streaming Video On-demand.Content Characteristics - Streaming Video Live. ![]() Content Characteristics - Dynamic Web Content.Cloud Interconnects for Microsoft Azure.Akamai Provider for Salesforce Commerce Cloud Host Header Control.Akamai Provider for Salesforce Commerce Cloud.Akamai Connector for Salesforce Commerce Cloud.The custom origin (publicly trusted certificate).
0 Comments
Leave a Reply. |