From 62c601a8de82bfcfe8272cea258d04eba68a617c Mon Sep 17 00:00:00 2001
From: Andre Malo This module allows for control of the environment that will
be provided to CGI scripts and SSI pages. Environment variables
may be passed from the shell which invoked the httpd process.
Alternatively, environment variables may be set or unset within
the configuration process. Specifies one or more environment variables to pass to CGI
scripts and SSI pages from the environment of the shell which
- invoked the httpd process. Example:
Sets an environment variable, which is then passed on to CGI - scripts and SSI pages. Example:
-Removes one or more environment variables from those passed - on to CGI scripts and SSI pages. Example:
-Expires HTTP headers according to user-specified
- criteriaExpires HTTP headers according to
+user-specified criteriaThe The where <base> is one of: The ' The
- ExpiresByType type/encoding "<base> [plus]
+ ExpiresByType type/encoding "<base> [plus]
{<num> <type>}*"
-modificationplus' keyword is optional. <num>
+ plus keyword is optional. <num>
should be an integer value [acceptable to atoi()],
and <type> is one of:
@@ -74,21 +65,21 @@
make documents expire 1 month after being accessed, by
default:yearsmonthsweeksdayshoursminutesseconds
The expiry time can be fine-tuned by adding several '<num> <type>' clauses:
-Note that if you use a modification date based setting, the
Expires header will not be added to content
@@ -98,7 +89,8 @@ ExpiresByType text/html "access plus 1 month 15
Expires headersExpires
+headersExpires header for the document realm in question.
(That is, if found in an .htaccess file, for
instance, it applies only to documents generated from that
- directory.) If set to Off, no
- Expires header will be generated for any document
- in the realm (unless overridden at a lower level, such as an
- .htaccess file overriding a server config file).
- If set to On, the header will be added to
- served documents according to the criteria defined by the
+ directory.) If set to Off, no Expires header
+ will be generated for any document in the realm (unless overridden at
+ a lower level, such as an .htaccess file overriding a
+ server config file). If set to On, the header will be
+ added to served documents according to the criteria defined by the
Expires header configured
by MIME typeThis 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.
text/html). The second argument sets the number of
+ seconds that will be added to a base time to construct the expiration
+ date.
The base time is either the last modification time of the
file, or the time of the client's access to the document. Which
should be used is specified by the
- <code> field; M
+ <code> field; M
means that the file's last modification time should be used as
- the base time, and A means the client's access
+ the base time, and A means the client's access
time should be used.
The difference in effect is subtle. If M is used, +
The difference in effect is subtle. If M is used,
all current copies of the document in all caches will expire at
the same time, which can be good for something like a weekly
- notice that's always found at the same URL. If A is
+ notice that's always found at the same URL. If A is
used, the date of expiration is different for each client; this
can be good for image files that don't change very often,
particularly for a set of related documents that all refer to
the same images (i.e., the images will be accessed
repeatedly within a relatively short timespan).
Example:
-Note that this directive only has effect if
ExpiresActive On has been specified. It overrides,
@@ -188,10 +178,9 @@ ExpiresByType text/html M604800