⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 mod_cache.html.en

📁 Apache官方在今天放出产品系列2.2的最新版本2.2.11的源码包 最流行的HTTP服务器软件之一
💻 EN
📖 第 1 页 / 共 3 页
字号:
    </code></p></div></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="CacheIgnoreQueryString" id="CacheIgnoreQueryString">CacheIgnoreQueryString</a> <a name="cacheignorequerystring" id="cacheignorequerystring">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Ignore query string when caching</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheIgnoreQueryString On|Off</code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheIgnoreQueryString Off</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.2.6 and later</td></tr></table>    <p>Ordinarily, requests with query string parameters are cached separately    for each unique query string. This is according to RFC 2616/13.9 done only    if an expiration time is specified. The     <code class="directive">CacheIgnoreQueryString</code> directive tells the cache to    cache requests even if no expiration time is specified, and to reply with     a cached reply even if the query string differs. From a caching point of    view the request is treated as if having no query string when this     directive is enabled.</p>    <div class="example"><p><code>      CacheIgnoreQueryString On    </code></p></div></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="CacheLastModifiedFactor" id="CacheLastModifiedFactor">CacheLastModifiedFactor</a> <a name="cachelastmodifiedfactor" id="cachelastmodifiedfactor">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The factor used to compute an expiry date based on theLastModified date.</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheLastModifiedFactor <var>float</var></code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheLastModifiedFactor 0.1</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></table>    <p>In the event that a document does not provide an expiry date but does    provide a last-modified date, an expiry date can be calculated based on    the time since the document was last modified. The    <code class="directive">CacheLastModifiedFactor</code> directive specifies a    <var>factor</var> to be used in the generation of this expiry date    according to the following formula:    <code>expiry-period = time-since-last-modified-date * <var>factor</var>    expiry-date = current-date + expiry-period</code>    For example, if the document was last modified 10 hours ago, and    <var>factor</var> is 0.1 then the expiry-period will be set to    10*0.1 = 1 hour. If the current time was 3:00pm then the computed    expiry-date would be 3:00pm + 1hour = 4:00pm.    If the expiry-period would be longer than that set by    <code class="directive">CacheMaxExpire</code>, then the latter takes    precedence.</p>    <div class="example"><p><code>      CacheLastModifiedFactor 0.5    </code></p></div></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="CacheMaxExpire" id="CacheMaxExpire">CacheMaxExpire</a> <a name="cachemaxexpire" id="cachemaxexpire">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The maximum time in seconds to cache a document</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheMaxExpire <var>seconds</var></code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheMaxExpire 86400 (one day)</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></table>    <p>The <code class="directive">CacheMaxExpire</code> directive specifies the maximum number of    seconds for which cachable 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.</p>    <div class="example"><p><code>      CacheMaxExpire 604800    </code></p></div></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="CacheStoreNoStore" id="CacheStoreNoStore">CacheStoreNoStore</a> <a name="cachestorenostore" id="cachestorenostore">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Attempt to cache requests or responses that have been marked as no-store.</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheStoreNoStore On|Off</code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheStoreNoStore Off</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></table>    <p>Ordinarily, requests or responses with Cache-Control: no-store header       values will not be stored in the cache.  The       <code class="directive">CacheStoreNoCache</code> directive allows this       behavior to be overridden.  <code class="directive">CacheStoreNoCache</code> On       tells the server to attempt to cache the resource even if it contains       no-store header values.  Resources requiring authorization will       <em>never</em> be cached.</p>    <div class="example"><p><code>      CacheStoreNoStore On    </code></p></div>    <div class="warning"><h3>Warning:</h3>       As described in RFC 2616, the no-store directive is intended to       "prevent the inadvertent release or retention of sensitive information       (for example, on backup tapes)."  Enabling this option could store       sensitive information in the cache.  You are hereby warned.    </div><h3>See also</h3><ul><li><code class="directive"><a href="#cacheignorecachecontrol">CacheIgnoreCacheControl</a></code></li><li><code class="directive"><a href="#cachestoreprivate">CacheStorePrivate</a></code></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="CacheStorePrivate" id="CacheStorePrivate">CacheStorePrivate</a> <a name="cachestoreprivate" id="cachestoreprivate">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Attempt to cache responses that the server has marked as private</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>CacheStorePrivate On|Off</code></td></tr><tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>CacheStorePrivate Off</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></table>    <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       tells the server to attempt to cache the resource even if it contains       private header values.  Resources requiring authorization will       <em>never</em> be cached.</p>    <div class="example"><p><code>      CacheStorePrivate On    </code></p></div>    <div class="warning"><h3>Warning:</h3>       This directive will allow caching even if the upstream server has       requested that the resource not be cached.  This directive is only       ideal for a 'private' cache.    </div><h3>See also</h3><ul><li><code class="directive"><a href="#cacheignorecachecontrol">CacheIgnoreCacheControl</a></code></li><li><code class="directive"><a href="#cachestorenostore">CacheStoreNoStore</a></code></li></ul></div></div><div class="bottomlang"><p><span>Available Languages: </span><a href="../en/mod/mod_cache.html" title="English">&nbsp;en&nbsp;</a> |<a href="../ja/mod/mod_cache.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |<a href="../ko/mod/mod_cache.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a></p></div><div id="footer"><p class="apache">Copyright 2008 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p><p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div></body></html>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -