Caching creates a copy of the requested content on our edge servers. This dramatically reduces the distance that the data has to travel to fulfill all future requests.
By default, caching has been disabled on the CAN platform, since it is designed to serve dynamic content that is typically unique.
Learn how to override this behavior.
By default, only GET requests that result in a 200 OK response are eligible to be cached.
There are three cache layers for assetA file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.s routed using our CAN service, which are CAN Gateway, edge server, and user agent caching. A brief explanation for each one is provided below.
A user can clear a web browser’s cache.
As mentioned above, the caching mechanism for the CAN Gateway and edge servers is disabled by default. However, if your customer origin server assigns a TTL to a request, then our servers will forward the corresponding header information (i.e., Cache-Control and Expires) to the user agent that requested it.
Rules Engine, which must be purchased separately, may be used to override the above behavior. For example, it can be configured to allow caching for certain types of requests on the CAN platform.
Learn more about the Bypass Cache feature.
For detailed information on when content is cached, please refer to the Request topic.
The following information is only applicable for requests where CDN caching has been enabled:
An asset's TTL is determined by its response headers.
Edgecast CDN