Support

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching > Ensuring cached object freshness
Ensuring cached object freshness
Help | Content Gateway | Version 7.7.3
When Content Gateway receives a request for a Web object, it tries to locate the requested object in its cache. If the object is in the cache, the proxy checks to see if the object is fresh enough to serve.
The protocol determines how the proxy handles object freshness in the cache:
*
HTTP objects support author-specified expiration dates. The proxy adheres to these expiration dates; otherwise, it picks an expiration date based on how frequently the object is changing and on administrator-chosen freshness guidelines. In addition, objects can be revalidated, checking with the origin server if an object is still fresh. See HTTP object freshness.
*
FTP objects stay in the cache for a specified time period. See FTP object freshness.
Print print article Email email article Font Size: A A

Search

Article Rating:

Do you have any additional feedback?    Email: close

Related Articles

Quick Links

Service Requests

How are we doing?

Provide us feedback on your experience with the Service Request portal.

provide feedback >

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching > Ensuring cached object freshness