Determining HTTP Response Cacheability
search cancel

Determining HTTP Response Cacheability


Article ID: 165652


Updated On:


ProxySG Software - SGOS


A response cannot be considered cacheable if the request was already deemed uncacheable.  If the request was considered cacheable, the response can still determine that it is uncacheable based on the following:

Note: The default value of 0 means cache negative  = N. The negative-response caching time can be configured with the following :

  • Auth
  • Cache-Control: private, no store, or no cache
  • Pragma: no-cache
  • Set-Cookie
  • Varies
  • www-auth

3. Type N object (object contains no info that would provide any insight into its expiration/refresh) with cookie or parameterized URL that is not overridden by config is not cacheable

5. The object is greater than the maximum cache size allowed

4. The response has no headers or the headers are greater than 8K then it is not cacheable

2. The presence of the following headers:

#(config caching) negative-response <minutes>

Specifies that negative responses should be cached for the specified time. Default is 0 minutes.

1. Response code