Show search and navigation.

 

Origin Shield Frequently Asked Questions

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
Origin ShieldThis feature provides a layer of protection for a customer origin server by creating an intermediate caching layer between it and our edge servers. This caching layer resides on one or more of our point-of-presence (POPs). Requests that have not been previously cached on a POP will be channelled through the closest origin shield server. The origin shield server will then either serve a cached version of the requested content or retrieve it from a customer origin server. This feature shifts the network load from the customer origin server to the CDN, since most requests will be handled by the origin shield server.
ClosedHow does Origin Shield work?

The Origin Shield feature reduces the number of requests that are sent to the customer origin server. This results in reduced server and network load on the customer origin server. It is able to accomplish this by establishing an intermediate caching layer between the customer origin server and an edge server.

Learn more.

ClosedWhat is the caching policy for an Origin Shield location?

Our standard caching policy for the HTTP Large and HTTP Small platforms also applies to an Origin Shield location.

ClosedWill updating a customer origin's Origin Shield location affect cached content?

No. Leveraging a different Origin Shield location will not affect content previously cached on it.

Updating a customer's Origin Shield location may result in a temporary increase in bandwidth as content is cached at the new location. This cache fill occurs when the new Origin Shield location handles traffic that has not been previously cached at that location.

ClosedShould I protect my customer origin using a single or multiple Origin Shield locations?

In order to reduce the number of requests directed to your web servers, it is recommended to only define a single Origin Shield location. This allows all requests that are not served from cache (i.e., directly from the edge of our network) to be funneled through the Origin Shield location closest to your web servers.

Defining additional locations or bypassing a region will cause more requests to be forwarded to your web servers.

More advanced customer origin configurations may benefit from using multiple Origin Shield locations. Please contact your CDN account manager to learn more information.

ClosedWhy can't I enable Origin Shield on a customer origin configuration?

If the Enable Origin Shield option is disabled, then the Origin Shield feature has not been activated on your customer account. Please contact your CDN account manager.

The Origin Shield feature is unavailable for the ADN platform.

More Information