Show search and navigation.
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.
Our standard caching policy for the HTTP Large and HTTP Small platforms also applies to an Origin Shield location.
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.
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.
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.