Support
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Client directives
|
By default, Content Gateway does not cache objects with the following request headers:
|
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.
|
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.
|
Quick Links
Service Requests
How are we doing?
Provide us feedback on your experience with the Service Request portal.
provide feedback >|
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Client directives
|
