GCS Amplitude
GCS Amplitude

Apache Module mod_cache_socache

Turn on caching CacheSocache shmcb CacheSocacheMaxSize 102400 CacheEnable socache

Fall back to the disk cache CacheSocache shmcb CacheSocacheMaxSize 102400 CacheEnable socache CacheEnable disk

implements a shared object cache (socache) based storage manager for modcachesocache

The headers and bodies of cached responses are combined, and stored underneath a single key in the shared object cache. A number of implementations of shared object caches are available to choose from.

Multiple content negotiated responses can be stored concurrently, however the caching of partial content is not yet supported by this module.

requires the services of modcachesocache

, which must be loaded before modcachesocache.mod_cache

module will only attempt to cache responses that have an explicit content length, or that are small enough to be written in one pass. This is done to allow the modcachesocache

module to have an opportunity to cache responses larger than those cacheable within modcachedisk

directive sets the amount of seconds beyond the freshness lifetime of the response that the response should be cached for in the shared object cache. If a response is only stored for its freshness lifetime, there will be no opportunity to revalidate the response to make it fresh again.

directive sets the minimum amount of data, in bytes, to be read from the backend before the data is sent to the client. The default of zero causes all data read of any size to be passed downstream to the client immediately as it arrives. Setting this to a higher value causes the disk cache to buffer at least this amount before sending the result to the client. This can improve performance when caching content from a slow reverse proxy.

This directive only takes effect when the data is being saved to the cache, as opposed to data being served from the cache.

The default of zero disables this option.

This directive only takes effect when the data is being saved to the cache, as opposed to data being served from the cache. It is recommended that this option be used alongside the

directive to ensure that the server does not buffer excessively should data arrive faster than expected.CacheSocacheReadSize

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.4

Apache Module mod_cache_socache

Available Languages: en | fr

CacheSocache Directive

The CacheSocache directive defines the name of the shared object cache implementation to use, followed by optional arguments for that implementation. A number of implementations of shared object caches are available to choose from.

CacheSocacheMaxSize Directive

The CacheSocacheMaxSize directive sets the maximum size, in bytes, for the combined headers and body of a document to be considered for storage in the cache. The larger the headers that are stored alongside the body, the smaller the body may be.

CacheSocacheMaxTime Directive

The CacheSocacheMaxTime directive sets the maximum freshness lifetime, in seconds, for a document to be stored in the cache. This value overrides the freshness lifetime defined for the document by the HTTP protocol.

CacheSocacheMinTime Directive

The CacheSocacheMinTime directive sets the amount of seconds beyond the freshness lifetime of the response that the response should be cached for in the shared object cache. If a response is only stored for its freshness lifetime, there will be no opportunity to revalidate the response to make it fr

CacheSocacheReadSize Directive

The CacheSocacheReadSize directive sets the minimum amount of data, in bytes, to be read from the backend before the data is sent to the client. The default of zero causes all data read of any size to be passed downstream to the client immediately as it arrives. Setting this to a higher value causes

CacheSocacheReadTime Directive

The CacheSocacheReadTime directive sets the minimum amount of elapsed time that should pass before making an attempt to send data downstream to the client. During the time period, data will be buffered before sending the result to the client. This can improve performance when caching content from a