Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Web Proxy Caching > Caching HTTP objects > Origin server directives > Configuring the proxy to ignore WWW-Authenticate headers
Configuring the proxy to ignore WWW-Authenticate headers
Help | Content Gateway | Version 8.2.x
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.
 
Important 
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.
Open the records.config file located in the Content Gateway config directory.
2.
 
Set to 1 to cache objects with WWW-Authenticate headers.
3.
4.
content_line -x

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Web Proxy Caching > Caching HTTP objects > Origin server directives > Configuring the proxy to ignore WWW-Authenticate headers
Copyright 2016 Forcepoint LLC. All rights reserved.