To cache or not to cache?

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 > To cache or not to cache?

To cache or not to cache?

Help | Content Gateway | Version 7.7.3

When Content Gateway receives a request for a Web object that is not in the cache, it retrieves the object from the origin server and serves it to the client. At the same time, the proxy checks if the object is cacheable before storing it in its cache to serve future requests.

Content Gateway determines if an object is cacheable based on protocol:

For HTTP objects, the proxy responds to caching directives from clients and origin servers. In addition, you can configure the proxy not to cache certain objects. See Caching HTTP objects.

For FTP objects, the proxy responds to caching directives you specify through configuration options and files. See Caching FTP objects.

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 > To cache or not to cache?