Property configuration features

Learn about common features you can implement in your property configuration.

Feature Description
Browser Cache-Control Headers Allows you to specify the caching response headers sent to the end-user browser based on the headers generated at your origin. If you enable this feature, you can:
  • Remove Default cache-busting headers and add Cache-Control = Private. For no-stored content, this replaces the standard cache-busting headers with the Private directive.
  • Pass through the origin's Cache-Control headers to the browser. Use the same Cache-Control headers as the origin sends in the response that is sent to the end user.
  • Add cache-busting headers to cacheable content and remove the default caching headers. Use this to replace any caching instructions that would go to the end user’s browser with no-store instructions.
  • Set a fixed TTL in cache in the Cache-Control header. This option removes the Expires header. Allows you to set a specific length of time the content should be available in the browser cache. This cancels any expire in the time/date instructions.
  • Pass through all origin cache-control headers. Passes through all caching instructions from origin, not just those sent with the Cache-Control header.
Cache Key: Query String Provides controls for the query string parameters that determine the cache key for a set of objects. By default, the server includes the query string portion of a request URL in the cache key. You can increase the cache hit rate for your objects by selectively including, or excluding, the query string parameters that define the uniqueness of the object.
You can choose to form the cache key by:
  • ignoring all query arguments;
  • ignoring specific query arguments by name; or
  • including specific query arguments by name, and ignoring all others.
Centralized / Basic Authentication Directs the server to forward every client request to the origin server for authorization. If the origin server is not available, the server will serve an error to the client.
Control Access by Referrer Domain With referrer checking enabled, the edge server can check the referrer header sent in the client request against a list, and reject requests that do not match.
Control Access by URL or IP Allows you to authorize or deny access to certain content based on the client IP address, path, and /or file extension.
Connection Timeouts and Persistent Connections You can modify timeouts for certain connections between the Edge Server and the origin only with the assistance of a service representative. The timeouts that may be modified include the HTTP Read timeout and, in some cases, the Edge-to-Origin persistent connection (PCONN) timeout.
Content Targeting Allows you to customize content based on parameters related to the end user’s connection, for example geographical location and connection speed. Learn more about Content Targeting.
CP Code Rules For particular paths or file extensions, CP code rules allow you to override either the default CP code or per-digital property settings with a different CP code. This type of override can
  • be useful for customizing the data aggregation for your reports, and
  • allow you to enhance purge-by-CP code functionality by tagging specific content with a unique CP code.
Device Characterization Provides additional ways to accelerate and optimize your content by taking into account a requesting device’s characteristics. Learn more about Device Characterization.
DNS Asynchronous Refresh Allows you to asynchronously update the origin DNS entry. The server will use a stale DNS response to serve the client, and at the same time start a refresh of the entry. If the DNS entry is more than two hours past its expiration, the entry will be refreshed before it is used to serve the client. When a DNS entry has expired, DNS Refresh helps avoid the unnecessary DNS name resolution delay. This feature is used to ensure optimal performance and reduce potential issues with the origin’s DNS entries.
Edge Server Identification Allows you to identify, through the use of a cookie, whether a request came from an edge server.
Honor HTTP Cache-Control and Expires Headers Allows the use of
  • HTTP Cache-Control response headers, associated with origin objects, to override max-age settings in this configuration, and
  • HTTP Expires response headers to set the expiration date and time.
Note: You cannot override no-store settings with Cache-Control or Expires headers.
Mobile Detection and Redirect Identifies incoming requests originating from mobile devices and, based on match rules that you define, sends those requests to the optimal site for the device. When an edge server receives an HTTP request, Mobile Detection and Redirect uses Device Characterization technology to identify the device. If the requesting device is mobile, then Mobile Detection and Redirect will:
  • look in the site’s configuration file for user-defined match rules;
  • get the device’s characteristics from Device Characterization; and
  • compare the device details, and the details of the original request, to the match rules’ detection settings.
Learn more about device information.
Modify Path Rules Normally the server requests content from the origin server by forwarding a request that includes the client request URL. This feature allows you to direct the request to a different location on the origin server and/or change the value of the origin server. The location you specify must be the complete URL beginning with a forward slash.
Redirect Allows an edge server to respond to a client request with a redirect without having to contact the origin server. The redirect can send the user to a different URI path and/or hostname. This feature can allow you to offload requests from your origin server.
Remove Vary Header By default, an object with an HTTP Vary header in the response is not cached. Some applications add this header even when the content does not vary. In that case, you can select this option to remove the header so that the content may be cached.
Set Cookies The servers can generate a unique or fixed-name cookie to send to the client without the need to contact the origin server. The cookie is set only if it is not already present in the client request. The unique cookie is a useful way to identify the number of unique users or analyze client sessions within a website.
Site Failover Lets you specify content to be served in the event that the origin server cannot be reached, or the content either does not exist or has expired. You can configure this feature to
  • serve a redirect to the client browser, or
  • recreate the request with a new hostname, which allows the server to apply new features and potentially fetch content from a different origin server.
Learn more about Site Failover.