|
AOLServer |
Apache |
Microsoft IIS |
Netscape iPlanet 6.0 |
Netscape iPlanet 4.x |
Netscape Enterprise Server 3.6
Netscape Enterprise Server 3.6 has built-in cache-control functionality. Using the cache-control directives, webmasters may determine the default rules for how their objects cached by a proxy server. Additionally, webmasters may override this default in order to protect sensitive information. It is necessary that the proxy server comply with HTTP 1.1 to utilize cache-control.
Cache-control directives can be set for specific directories. The following are a list of caching levels as taken from the Netscape Enterprise Server Administrator's Guide for Unix:
Public — The response is cacheable by any cache.
Private — The response is only cacheable by a private (nonshared) cache.
No cache — The response must not be cached anywhere.
No store — The cache must not store the request or response anywhere in nonvolatile storage.
Must revalidate — The cache entry must be revalidated from the originating server.
Maximum age — In seconds. The client does not accept a response that has an age greater than this age.
To set the cache-control directives on the server, please use the following instructions:
- Choose Content Management|Cache Control Directives
- From the Resource Picker, choose the directory or directories for which you want to set cache-control directives
- Choose the level of control you want to set; the default is public
- Click OK
For more information, go to http://developer.netscape.com/docs/manuals/enterprise/admnunix/content.htm#1006282
| 
