Technical Library | Support

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 > Client directives
Client directives
Help | Content Gateway | Version 8.0.x
By default, Content Gateway does not cache objects with the following request headers:
*
Cache-Control: no-store
*
Cache-Control: no-cache
 
* 
Note 
You can configure the proxy to ignore the Cache-Control: no-cache header. See Configuring the proxy to ignore client no-cache headers.
*
Cookie: (for text objects)
By default, the proxy caches objects served in response to requests that contain cookies unless the object is text. You can configure the proxy to not cache cookied content of any type, cache all cookied content, or cache cookied content that is of image type only. See Caching cookied objects.
*
Authorization:
 
* 
Note 
FTP objects requested from HTTP clients can also contain Cache-Control: no-store, Cache-Control: no-cache, or Authorization headers. If an FTP object requested from an HTTP client contains such a header, the proxy does not cache it unless explicitly configured to do so.

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 > Client directives
Copyright 2016 Forcepoint LLC. All rights reserved.