Revert invalid 2.4.28/38 tagging.

                                                         -*- coding: utf-8 -*-

Changes with Apache 2.4.39

Changes with Apache 2.4.38

  *) mod_ssl: Clear retry flag before aborting client-initiated renegotiation.

    [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,

          while x.{even}.z versions are Stable/GA releases.]

    2.4.39  : In development

    2.4.38  : Tagged on January 17, 2019

    2.4.38  : In development

    2.4.37  : Tagged on October 18, 2018. Released on October 23, 2018.

    2.4.36  : Tagged on October 10, 2018. Not released.

    2.4.35  : Tagged on September 17, 2018. Released on September 22, 2018. 

  server, a significant number of requests might arrive during this time, and

  cause a <strong>thundering herd</strong> of requests to strike the backend

  suddenly and unpredictably.</p>

  <p>To keep the thundering herd at bay, the <code class="directive"><a href="#cachelock">CacheLock</a></code>

  <p>To keep the thundering herd at bay, the <code class="directive">CacheLock</code>

  directive can be used to define a directory in which locks are created for

  URLs <strong>in flight</strong>. The lock is used as a <strong>hint</strong>

  by other requests to either suppress an attempt to cache (someone else has

    <p>As a further safety mechanism, locks have a configurable maximum age.

    Once this age has been reached, the lock is removed, and a new request is

    given the opportunity to create a new lock. This maximum age can be set using

    the <code class="directive"><a href="#cachelockmaxage">CacheLockMaxAge</a></code> directive, and defaults

    to 5 seconds.

    the <code class="directive">CacheLockMaxAge</code> directive, and defaults to 5

    seconds.

    </p>

  <h3>Example configuration</h3>

  <p>While this mode offers the best performance, the administrator may find that

  under certain circumstances they may want to perform further processing on the

  request after the request is cached, such as to inject personalisation into the

  cached page, or to apply authorization restrictions to the content. Under these

  cached page, or to apply authorisation restrictions to the content. Under these

  circumstances, an administrator is often forced to place independent reverse

  proxy servers either behind or in front of the caching server to achieve this.</p>

  <p>To solve this problem the <code class="directive"><a href="#cachequickhandler">CacheQuickHandler</a></code>

  directive can be set to <strong>off</strong>, and the server will

  <p>To solve this problem the <code class="directive"><a href="#cachequickhandler">CacheQuickHandler

  </a></code> directive can be set to <strong>off</strong>, and the server will

  process all phases normally handled by a non-cached request, including the

  <strong>authentication and authorization</strong> phases.</p>

  <strong>authentication and authorisation</strong> phases.</p>

  <p>In addition, the administrator may optionally specify the <strong>precise point

  within the filter chain</strong> where caching is to take place by adding the

</table>

    <p>The <code class="directive">CacheDefaultExpire</code> directive specifies a default time,

    in seconds, to cache a document if neither an expiry date nor last-modified date are provided

    with the document. The value specified with the <code class="directive"><a href="#cachemaxexpire">CacheMaxExpire</a></code>

    with the document. The value specified with the <code class="directive">CacheMaxExpire</code>

    directive does <em>not</em> override this setting.</p>

    <pre class="prettyprint lang-config">CacheDefaultExpire 86400</pre>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.3.9 and later</td></tr>

</table>

  <p>When the <code class="directive">CacheDetailHeader</code> directive

  <p>When the <code class="directive"><a href="#cachedetailheader">CacheDetailHeader</a></code> directive

  is switched on, an <strong>X-Cache-Detail</strong> header will be added to the response

  containing the detailed reason for a particular caching decision.</p>

    <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">CacheDisable "/local_files"</pre>

</div>

    <p>If used in a <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> directive,

    <p>If used in a <code class="directive">&lt;Location&gt;</code> directive,

    the path needs to be specified below the Location, or if the word "on"

    is used, caching for the whole location will be disabled.</p>

    <var>url-string</var>. The cache storage manager is specified with the

    <var>cache_type</var> argument. The <code class="directive">CacheEnable</code>

    directive can alternatively be placed inside either

    <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> or

    <code class="directive"><a href="../mod/core.html#locationmatch">&lt;LocationMatch&gt;</a></code> sections to indicate

    <code class="directive">&lt;Location&gt;</code> or

    <code class="directive">&lt;LocationMatch&gt;</code> sections to indicate

    the content is cacheable.

    <var>cache_type</var> <code>disk</code> instructs

    <code class="module"><a href="../mod/mod_cache.html">mod_cache</a></code> to use the disk based storage manager

    actually processes the request. The order in which the storage managers are

    run is determined by the order of the <code class="directive">CacheEnable</code>

    directives in the configuration file. <code class="directive">CacheEnable</code>

    directives within <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code> or

    <code class="directive"><a href="../mod/core.html#locationmatch">&lt;LocationMatch&gt;</a></code> sections are processed

    directives within <code class="directive">&lt;Location&gt;</code> or

    <code class="directive">&lt;LocationMatch&gt;</code> sections are processed

    before globally defined <code class="directive">CacheEnable</code> directives.</p>

    <p>When acting as a forward proxy server, <var>url-string</var> must

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.3.9 and later</td></tr>

</table>

  <p>When the <code class="directive">CacheHeader</code> directive

  <p>When the <code class="directive"><a href="#cacheheader">CacheHeader</a></code> directive

  is switched on, an <strong>X-Cache</strong> header will be added to the response

  with the cache status of this response. If the normal handler is used, this

  directive may appear within a <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>

<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

</table>

    <p>Ordinarily, requests containing a <code>Cache-Control: no-cache</code> or

    <p>Ordinarily, requests containing a Cache-Control: no-cache or

    Pragma: no-cache header value will not be served from the cache.  The

    <code class="directive">CacheIgnoreCacheControl</code> directive allows this

    behavior to be overridden.  <code class="directive">CacheIgnoreCacheControl On</code>

    should be considered for caching, even without a last-modified date.

    If neither a last-modified date nor an expiry date are provided with

    the document then the value specified by the

    <code class="directive"><a href="#cachedefaultexpire">CacheDefaultExpire</a></code> directive will be used to

    <code class="directive">CacheDefaultExpire</code> directive will be used to

    generate an expiration date.</p>

    <pre class="prettyprint lang-config">CacheIgnoreNoLastMod On</pre>

<table class="directive">

<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Override the base URL of reverse proxied cache keys.</td></tr>

<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheKeyBaseURL <var>URL</var></code></td></tr>

<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheKeyBaseURL http://example.com</code></td></tr>

<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host</td></tr>

<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.3.9 and later</td></tr>

</table>

  <p>When the <code class="directive">CacheKeyBaseURL</code> directive

  <p>When the <code class="directive"><a href="#cachekeybaseurl">CacheKeyBaseURL</a></code> directive

  is specified, the URL provided will be used as the base URL to calculate

  the URL of the cache keys in the reverse proxy configuration. When not specified,

  the scheme, hostname and port of the current virtual host is used to construct

    expiry-date would be 3:00pm + 1hour = 4:00pm.

    If the expiry-period would be longer than that set by

    <code class="directive"><a href="#cachemaxexpire">CacheMaxExpire</a></code>, then the latter takes

    <code class="directive">CacheMaxExpire</code>, then the latter takes

    precedence.</p>

    <pre class="prettyprint lang-config">CacheLastModifiedFactor 0.5</pre>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Apache HTTP Server 2.3.3 and later</td></tr>

</table>

    <p>The <code class="directive">CacheQuickHandler</code> directive

    <p>The <code class="directive"><a href="#cachequickhandler">CacheQuickHandler</a></code> directive

    controls the phase in which the cache is handled.</p>

    <p>In the default enabled configuration, the cache operates within the quick

    <p>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.</p>

    processing is required, such as when content is subject to authorisation.</p>

    <pre class="prettyprint lang-config"># Run cache as a normal handler

CacheQuickHandler off</pre>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 2.3.9 and later</td></tr>

</table>

  <p>When the <code class="directive">CacheStaleOnError</code> directive

  <p>When the <code class="directive"><a href="#cachestaleonerror">CacheStaleOnError</a></code> 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,

<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

</table>

    <p>Ordinarily, requests or responses with <code>Cache-Control: no-store</code> header

    <p>Ordinarily, requests or responses with Cache-Control: no-store header

       values will not be stored in the cache.  The

       <code class="directive">CacheStoreNoStore</code> directive allows this

       behavior to be overridden.  <code class="directive">CacheStoreNoStore</code> On

<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_cache</td></tr>

</table>

    <p>Ordinarily, responses with <code>Cache-Control: private</code> header values will not

    <p>Ordinarily, responses with Cache-Control: private header values will not

       be stored in the cache.  The <code class="directive">CacheStorePrivate</code>

       directive allows this behavior to be overridden.

       <code class="directive">CacheStorePrivate</code> On

<table class="directive">

<tr><th><a href="directive-dict.html#Description">説明:</a></th><td>Override the base URL of reverse proxied cache keys.</td></tr>

<tr><th><a href="directive-dict.html#Syntax">構文:</a></th><td><code>CacheKeyBaseURL <var>URL</var></code></td></tr>

<tr><th><a href="directive-dict.html#Default">デフォルト:</a></th><td><code>CacheKeyBaseURL http://example.com</code></td></tr>

<tr><th><a href="directive-dict.html#Context">コンテキスト:</a></th><td>サーバ設定ファイル, バーチャルホスト</td></tr>

<tr><th><a href="directive-dict.html#Status">ステータス:</a></th><td>Extension</td></tr>

<tr><th><a href="directive-dict.html#Module">モジュール:</a></th><td>mod_cache</td></tr>

<p><span>Langues Disponibles: </span><a href="../en/mod/mod_lua.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |

<a href="../fr/mod/mod_lua.html" title="Français">&nbsp;fr&nbsp;</a></p>

</div>

<div class="outofdate">Cette traduction peut être périmée. Vérifiez la version

            anglaise pour les changements récents.</div>

<table class="module"><tr><th><a href="module-dict.html#Description">Description:</a></th><td>Fournit des points d'entrée Lua dans différentes parties du

traitement des requêtes httpd</td></tr>

<tr><th><a href="module-dict.html#Status">Statut:</a></th><td>Expérimental</td></tr>