In a minimal configuration the following directive is all that is needed to enable the thundering herd lock in the default system temp directory. The CacheLockMaxAge directive specifies the maximum age of any cache lock. A lock older than this value in seconds will be ignored, and the next incoming request will be given the opportunity to re-establish the lock.
This mechanism prevents a slow client taking an excessively long time to refresh an entity. The CacheLockPath directive allows you to specify the directory in which the locks are created. By default, the system's temporary folder is used. Locks consist of empty files that only exist for stale URLs in flight, so is significantly less resource intensive than the traditional disk cache.
The CacheMaxExpire directive specifies the maximum number of seconds for which cacheable HTTP documents will be retained without checking the origin server. Thus, documents will be out of date at most this number of seconds. This maximum value is enforced even if an expiry date was supplied with the document. The CacheMinExpire directive specifies the minimum number of seconds for which cacheable HTTP documents will be retained without checking the origin server.
This is only used if no valid expire time was supplied with the document. The CacheQuickHandler directive controls the phase in which the cache is handled.
In the default enabled configuration, the cache operates within the quick handler phase. This phase short circuits the majority of server processing, and represents the most performant mode of operation for a typical server.
The cache bolts onto the front of the server, and the majority of server processing is avoided. When disabled, the cache operates as a normal handler, and is subject to the full set of phases when handling a server request. While this mode is slower than the default, it allows the cache to be used in cases where full processing is required, such as when content is subject to authorization. It is also possible, when the quick handler is disabled, for the administrator to choose the precise location within the filter chain where caching is to be performed, by adding the CACHE filter to the chain.
When the CacheStaleOnError directive is switched on, and when stale data is available in the cache, the cache will respond to 5xx responses from the backend by returning the stale data instead of the 5xx response. While the Cache-Control headers sent by clients will be respected, and the raw 5xx responses returned to the client on request, the 5xx response so returned to the client will not invalidate the content in the cache.
Since httpd 2. The CacheStoreExpired directive allows this behavior to be overridden. CacheStoreExpired On tells the server to attempt to cache the resource if it is stale. Subsequent requests would trigger an If-Modified-Since request of the origin server, and the response may be fulfilled from cache if the backend resource has not changed.
Ordinarily, requests or responses with Cache-Control: no-store header values will not be stored in the cache. The CacheStoreNoStore directive allows this behavior to be overridden.
CacheStoreNoStore On tells the server to attempt to cache the resource even if it contains no-store header values. Ordinarily, responses with Cache-Control: private header values will not be stored in the cache. The CacheStorePrivate directive allows this behavior to be overridden. CacheStorePrivate On tells the server to attempt to cache the resource even if it contains private header values. Copyright The Apache Software Foundation. Licensed under the Apache License, Version 2.
This module should be used with care, as when the CacheQuickHandler directive is in its default value of on , the Allow and Deny directives will be circumvented. You should not enable quick handler caching for any content to which you wish to limit access by client host name, address or environment variable.
Sample Configuration Sample httpd. Initial caching of an entry When an entity is cached for the first time, a lock will be created for the entity until the response has been fully cached. Refreshment of a stale entry When an entity reaches its freshness lifetime and becomes stale, a lock will be created for the entity until the response has either been confirmed as still fresh, or replaced by the backend. Locks and Cache-Control: no-cache Locks are used as a hint only to enable the cache to be more gentle on backend servers, however the lock can be overridden if necessary.
Fine Control with the CACHE Filter Under the default mode of cache operation, the cache runs as a quick handler, short circuiting the majority of server processing and offering the highest cache performance available. This makes it possible to support conditional logging of cached requests as per the following example: CustomLog "cached-requests. CacheDefaultExpire Directive Description: The default duration to cache a document when no expiry date is specified.
CacheDefaultExpire Match www. See also Environment Variables in Apache. HIT The entity was fresh, and was served from cache. MISS The entity was fetched from the upstream server and was not served from cache.
CacheIgnoreCacheControl On Warning: This directive will allow serving from the cache even if the client has requested that the document not be served from the cache. This might result in stale content being served. Syntax: CacheIgnoreHeaders header-string [ header-string ] Example 2 CacheIgnoreHeaders None.
CacheIgnoreQueryString On. Override the base URL of the cache key. If two separate virtual hosts are accidentally given the same base URL, entries from one virtual host will be served to the other.
CacheLastModifiedFactor 0. CacheLock Directive Description: Enable the thundering herd lock. Enable cache lock CacheLock on. CacheMaxExpire CacheMinExpire Run cache as a normal handler CacheQuickHandler off It is also possible, when the quick handler is disabled, for the administrator to choose the precise location within the filter chain where caching is to be performed, by adding the CACHE filter to the chain.
Serve stale data on error. CacheStaleOnError on. CacheStoreExpired On. CacheStoreNoStore On Warning: As described in RFC , the no-store directive is intended to "prevent the inadvertent release or retention of sensitive information for example, on backup tapes.
This item will only be visible to you, admins, and anyone marked as a creator. Current visibility: Friends-only. This item will only be visible in searches to you, your friends, and admins. Description Discussions 10 Comments Change Notes. Description Discussions Comments Change Notes.
Add to Collection. This item has been added to your Favorites. File Size. Created by. See all collections some may be hidden. Subscribe to download akka's Interior Decor Structures. This item has been added to your Subscriptions. Some games will require you to relaunch them before the item will be downloaded. Various indoor decorations and furniture.
Mod ID: Creating these mods is very time consuming, if you like my mods and want to support their development:. Popular Discussions View All ThatNameThor 31 Oct am. There shouldn't be any issues with eco's mods, I've used many of them without any problems. ThatNameThor 30 Oct pm. Kalypso 9 Sep pm.
OMG, The Mod, i love it! Valentine 25 Aug pm. That makes a lot of sense!
0コメント