Cache exclusions
Some files and documents are never cached. These include the following:
- Files returned from requests using HTTP methods other than GET, such as
POST and PUT.
- Any documents requiring authentication, unless caching such documents
is specifically allowed by the origin server.
- The dynamic output of any CGI script (because this is unique each time
it is requested). Dynamically generated results from servlets and JavaServer
Pages (JSP) executed by IBM® WebSphere® Application Server can be cached if dynamic caching is enabled.
Refer to Caching dynamically generated content for details.
- Any information passed on an SSL tunneling connection (because
the proxy cannot decrypt the data passing through it).
- Any file returned from a URL containing a question mark (?), unless query
caching is specifically allowed. (Refer to Controlling what is cached for information
about configuring query results caching.)
It is possible to further restrict the items cached by setting caching
filters. For example, you might not want the proxy server to cache files that are
served locally from the proxy. Refer to Controlling what is cached for details.