Lines 469-478
Link Here
|
469 |
</contextlist> |
469 |
</contextlist> |
470 |
|
470 |
|
471 |
<usage> |
471 |
<usage> |
472 |
<p>The <directive>CacheMaxExpire</directive> directive specifies the maximum number of |
472 |
<p>The <directive>CacheMaxExpire</directive> directive specifies a maximum on the number |
473 |
seconds for which cachable HTTP documents will be retained without checking the origin |
473 |
of seconds for which cachable HTTP documents will be retained without checking the origin |
474 |
server. Thus, documents will be out of date at most this number of seconds. This maximum |
474 |
server. This maximum time is only used if a last-modified date is specified and no expiry |
475 |
value is enforced even if an expiry date was supplied with the document.</p> |
475 |
date is provided with the document, such as an Expires or a max-age header.</p> |
476 |
|
476 |
|
477 |
<highlight language="config"> |
477 |
<highlight language="config"> |
478 |
CacheMaxExpire 604800 |
478 |
CacheMaxExpire 604800 |
Lines 492-502
Link Here
|
492 |
</contextlist> |
492 |
</contextlist> |
493 |
|
493 |
|
494 |
<usage> |
494 |
<usage> |
495 |
<p>The <directive>CacheMinExpire</directive> directive specifies the minimum number of |
495 |
<p>The <directive>CacheMinExpire</directive> directive specifies a minimum number of |
496 |
seconds for which cachable HTTP documents will be retained without checking the origin |
496 |
seconds for which cachable HTTP documents will be retained without checking the origin |
497 |
server. This is only used if no valid expire time was supplied with the document.</p> |
497 |
server. This minimum time is only used if a last-modified date is specified and no expiry |
|
|
498 |
date is provided with the document, such as an Expires or a max-age header.</p> |
498 |
|
499 |
|
499 |
|
|
|
500 |
<highlight language="config"> |
500 |
<highlight language="config"> |
501 |
CacheMinExpire 3600 |
501 |
CacheMinExpire 3600 |
502 |
</highlight> |
502 |
</highlight> |