mod_cache implements an RFC 2616 compliant HTTP content cache that can be used to cache either local or proxied content. mod_cache requires the services of one or more storage management modules. Two storage management modules are included in the base Apache distribution:
Content stored and retrived keyed to the URL. Content with access protections is not cached.
The
The
The maximum time in seconds to cache a document. The
The default time in seconds to cache a document if the page does not have an expiry date in the Expires field.
Ignore responses where there is no Last Modified Header
Ignore requests from the client for uncached content
The factor used to estimate the Expires date from the LastModified date.
Percentage of download to arrive for the cache to force complete transfert.
Maximum number of bytes of a streamed response (i.e., a response where the entire content is not available all at once, such as a proxy or CGI response) to buffer before deciding if the response is cacheable. By default, a streamed response will not be cached unless it has a Content-Length header. The reason for this is to avoid using a large amount of memory to buffer a partial response that might end up being too large to fit in the cache anyway. To enable caching of streamed responses, use CacheMaxStreamingBuffer to specify the maximum amount of buffer space to use per request.
Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay the transmission of the response to the client. As soon as mod_cache copies a block of streamed content into a buffer, it sends the block on to the next output filter for delivery to the client.