Content Gateway Help
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Origin server directives > Configuring the proxy to ignore WWW-Authenticate headers
|
By default, Content Gateway does not cache objects that contain WWW-Authenticate response headers. The WWW-Authenticate header contains authentication parameters that the client uses when preparing the authentication challenge response to an origin server.
The default behavior of not caching objects with WWW-Authenticate headers is appropriate in most cases. Configure the proxy to ignore server WWW-Authenticate headers only if you are knowledgeable about HTTP 1.1.You can configure the proxy to ignore origin server WWW-Authenticate headers, in which case, objects with WWW-Authenticate headers are stored in the cache for future requests.
1.
proxy.config.http.cache.ignore_authentication
4.
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Origin server directives > Configuring the proxy to ignore WWW-Authenticate headers
|