From: Joshua Slive Date: Wed, 11 Aug 2004 16:59:41 +0000 (+0000) Subject: Note that mod_expires also sends Cache-Control: max-age. X-Git-Tag: post_ajp_proxy~76 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=820c63d2f9e1c9a7b4ec7f98a65667c428724037;p=apache Note that mod_expires also sends Cache-Control: max-age. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@104550 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/index.html.en b/docs/manual/mod/index.html.en index 3df53a8653..a265b114a9 100644 --- a/docs/manual/mod/index.html.en +++ b/docs/manual/mod/index.html.en @@ -114,8 +114,9 @@ modules
mod_env
Modifies the environment which is passed to CGI scripts and SSI pages
mod_example
Illustrates the Apache module API
-
mod_expires
Generation of Expires HTTP headers according to -user-specified criteria
+
mod_expires
Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
mod_ext_filter
Pass the response body through an external program before delivery to the client
mod_file_cache
Caches a static list of files in memory
diff --git a/docs/manual/mod/mod_expires.html.en b/docs/manual/mod/mod_expires.html.en index ebe6b04863..571d9d64ca 100644 --- a/docs/manual/mod/mod_expires.html.en +++ b/docs/manual/mod/mod_expires.html.en @@ -25,24 +25,32 @@  ja  |  ko 

- +
Description:Generation of Expires HTTP headers according to -user-specified criteria
Description:Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
Status:Extension
Module Identifier:expires_module
Source File:mod_expires.c

Summary

This module controls the setting of the Expires - HTTP header in server responses. The expiration date can set to - be relative to either the time the source file was last - modified, or to the time of the client access.

- -

The Expires HTTP header is an instruction to - the client about the document's validity and persistence. If - cached, the document may be fetched from the cache rather than - from the source until this time has passed. After that, the - cache copy is considered "expired" and invalid, and a new copy - must be obtained from the source.

+ HTTP header and the max-age directive of the + Cache-Control HTTP header in server responses. The + expiration date can set to be relative to either the time the + source file was last modified, or to the time of the client + access.

+ +

These HTTP headers are an instruction to the client about the + document's validity and persistence. If cached, the document may + be fetched from the cache rather than from the source until this + time has passed. After that, the cache copy is considered + "expired" and invalid, and a new copy must be obtained from the + source.

+ +

To modify Cache-Control directives other than + max-age (see RFC + 2616 section 14.9), you can use the Header directive.

+

Directives

top

ExpiresByType Directive

@@ -161,10 +171,13 @@ by MIME type Module:mod_expires

This directive defines the value of the Expires - header generated for documents of the specified type (e.g., - text/html). The second argument sets the number of - seconds that will be added to a base time to construct the expiration - date.

+ header and the max-age directive of the + Cache-Control header generated for documents of the + specified type (e.g., text/html). The second + argument sets the number of seconds that will be added to a base + time to construct the expiration date. The Cache-Control: + max-age is calculated by subtracting the request time from + the expiration date and expressing the result in seconds.

The base time is either the last modification time of the file, or the time of the client's access to the document. Which diff --git a/docs/manual/mod/mod_expires.xml b/docs/manual/mod/mod_expires.xml index 2ae7f5b45d..766983d649 100644 --- a/docs/manual/mod/mod_expires.xml +++ b/docs/manual/mod/mod_expires.xml @@ -1,7 +1,7 @@ - +