diff options
author | Joshua Slive <slive@apache.org> | 2000-09-28 22:43:31 +0000 |
---|---|---|
committer | Joshua Slive <slive@apache.org> | 2000-09-28 22:43:31 +0000 |
commit | f57744efd33eb7091157a2163d283e18d520d997 (patch) | |
tree | 841ca92ea5c752b061bd70bd863631f354b2fe21 | |
parent | 2582da8a2e364ed80c659fd2441ffb7327ec4e61 (diff) | |
download | httpd-f57744efd33eb7091157a2163d283e18d520d997.tar.gz |
Last of the module style changes (I hope).
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86351 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r-- | docs/manual/mod/mod_cgi.html | 5 | ||||
-rw-r--r-- | docs/manual/mod/mod_example.html | 44 | ||||
-rw-r--r-- | docs/manual/mod/mod_negotiation.html | 2 | ||||
-rw-r--r-- | docs/manual/mod/mod_rewrite.html | 32 | ||||
-rw-r--r-- | docs/manual/mod/mod_usertrack.html | 136 | ||||
-rw-r--r-- | docs/manual/mod/mod_vhost_alias.html | 8 |
6 files changed, 142 insertions, 85 deletions
diff --git a/docs/manual/mod/mod_cgi.html b/docs/manual/mod/mod_cgi.html index a40b525537..0b745bd2e7 100644 --- a/docs/manual/mod/mod_cgi.html +++ b/docs/manual/mod/mod_cgi.html @@ -61,8 +61,9 @@ configuration variable. </ul> <p>See also: <a href="core.html#options">Options</a>, <a -href="mod_alias.html#scriptalias">ScriptAlias</a> and <a -href="mod_mime.html#addtype">AddType</a>. +href="mod_alias.html#scriptalias">ScriptAlias</a>, <a +href="mod_mime.html#addtype">AddType</a> and <a +href="mod_mime.html#addhandler">AddHandler</a>. <H2>CGI Environment variables</H2> The server will set the CGI environment variables as described in the diff --git a/docs/manual/mod/mod_example.html b/docs/manual/mod/mod_example.html index 3cee4b97a8..f302361d5b 100644 --- a/docs/manual/mod/mod_example.html +++ b/docs/manual/mod/mod_example.html @@ -14,8 +14,7 @@ <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Module mod_example</H1> <P> - This module is contained in the <CODE>modules/mod_example.c</CODE> file, and - <STRONG>is not</STRONG> compiled in by default. It illustrates many of + This module illustrates many of the aspects of the <A HREF="../misc/API.html" @@ -24,6 +23,24 @@ and, when used, demonstrates the manner in which module callbacks are triggered by the server. </P> + +<P><A +HREF="module-dict.html#Status" +REL="Help" +><STRONG>Status:</STRONG></A> Extension +<BR> +<A +HREF="module-dict.html#SourceFile" +REL="Help" +><STRONG>Source File:</STRONG></A> mod_example.c +<BR> +<A +HREF="module-dict.html#ModuleIdentifier" +REL="Help" +><STRONG>Module Identifier:</STRONG></A> example_module +</P> + + <H2>Summary</H2> <P> The files in the <CODE>src/modules/example directory</CODE> under the @@ -43,6 +60,15 @@ some of the tracing the example module did as the various callbacks were made. </P> + <H2>Directives</H2> + <P> + <UL> + <LI><A HREF="#example">Example</A> + </LI> + </UL> + </P> + + <h2>Compiling the example module</h2> <P> To include the example module in your server, follow the steps below: </P> @@ -78,9 +104,9 @@ <LI>Follow steps [1] through [3] above, with appropriate changes. </LI> </OL> - <H3> + <H2> Using the <SAMP>mod_example</SAMP> Module - </H3> + </H2> <P> To activate the example module, include a block similar to the following in your <SAMP>srm.conf</SAMP> file: @@ -105,16 +131,10 @@ After reloading/restarting your server, you should be able to browse to this location and see the brief display mentioned earlier. </P> - <H2>Directives</H2> - <P> - <UL> - <LI><A HREF="#example">Example</A> - </LI> - </UL> - </P> + <HR> <H2><A NAME="example"> - Example + Example directive </A></H2> <P> <A diff --git a/docs/manual/mod/mod_negotiation.html b/docs/manual/mod/mod_negotiation.html index 2d8249019f..8e1a7ed8da 100644 --- a/docs/manual/mod/mod_negotiation.html +++ b/docs/manual/mod/mod_negotiation.html @@ -58,7 +58,7 @@ filename pattern match, and choose from amongst the results. <A HREF="./mod_mime.html#addencoding">AddEncoding</A>, <A HREF="./mod_mime.html#addlanguage">AddLanguage</A>, <A HREF="./mod_mime.html#addtype">AddType</A>, and -<A HREF="core.html#options">Option</A>. +<A HREF="core.html#options">Options</A>. <H2>Type maps</H2> A type map has the same format as RFC822 mail headers. It contains document diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index e891b1da4a..86135dfe8b 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -21,14 +21,30 @@ <BR> <H1 ALIGN="CENTER">Module mod_rewrite<BR>URL Rewriting Engine</H1> -This module is contained in the <CODE>mod_rewrite.c</CODE> file, with Apache -1.2 and later. It provides a rule-based rewriting engine to rewrite requested -URLs on the fly. It is not compiled into the server by default. To use -<CODE>mod_rewrite</CODE> you have to enable the following line in the server -build <CODE>Configuration</CODE> file: -<PRE> - AddModule modules/standard/mod_rewrite.o -</PRE> +<p>This module provides a rule-based rewriting engine to rewrite requested +URLs on the fly.</p> + +<P><A +HREF="module-dict.html#Status" +REL="Help" +><STRONG>Status:</STRONG></A> Extension +<BR> +<A +HREF="module-dict.html#SourceFile" +REL="Help" +><STRONG>Source File:</STRONG></A> mod_rewrite.c +<BR> +<A +HREF="module-dict.html#ModuleIdentifier" +REL="Help" +><STRONG>Module Identifier:</STRONG></A> rewrite_module +<BR> +<A +HREF="module-dict.html#Compatibility" +REL="Help" +><STRONG>Compatibility:</STRONG></A> Available in Apache 1.2 and later. +</P> + <P> <HR NOSHADE SIZE=1> diff --git a/docs/manual/mod/mod_usertrack.html b/docs/manual/mod/mod_usertrack.html index 87d81ac0f6..51099659af 100644 --- a/docs/manual/mod/mod_usertrack.html +++ b/docs/manual/mod/mod_usertrack.html @@ -15,25 +15,57 @@ <!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Module mod_usertrack</H1> -Previous releases of Apache have included a module which generates a +<p>This module uses cookies to provide for a <em>clickstream</em> log of user +activity on a site.</p> + +<P><A +HREF="module-dict.html#Status" +REL="Help" +><STRONG>Status:</STRONG></A> Extension +<BR> +<A +HREF="module-dict.html#SourceFile" +REL="Help" +><STRONG>Source File:</STRONG></A> mod_usertrack.c +<BR> +<A +HREF="module-dict.html#ModuleIdentifier" +REL="Help" +><STRONG>Module Identifier:</STRONG></A> usertrack_module +<BR> +<A +HREF="module-dict.html#Compatibility" +REL="Help" +><STRONG>Compatibility:</STRONG></A> Known as mod_cookies prior to +Apache 1.3. +</P> + +<h2>Summary</h2> + +<p>Previous releases of Apache have included a module which generates a 'clickstream' log of user activity on a site using cookies. This was called the "cookies" module, mod_cookies. In Apache 1.2 and later this module has been renamed the "user tracking" module, mod_usertrack. This module has been simplified and new directives -added. +added.</p> -<HR> +<H2>Directives</H2> + +<UL> +<LI><A HREF="#cookieexpires">CookieExpires</A> +<LI><A HREF="#cookiename">CookieName</A> +<LI><A HREF="#cookietracking">CookieTracking</A> +</UL> <H2>Logging</H2> -Previously, the cookies module (now the user tracking module) did its +<p>Previously, the cookies module (now the user tracking module) did its own logging, using the <TT>CookieLog</TT> directive. In this release, this module does no logging at all. Instead, a configurable log format file should be used to log user click-streams. This is possible because the logging module now allows <A HREF="../multilogs.html">multiple log files</A>. The cookie itself is logged by using the text <TT>%{cookie}n </TT> - in the log file format. For example: <PRE> CustomLog logs/clickstream "%{cookie}n %r %t" @@ -43,17 +75,50 @@ For backward compatibility the configurable log module implements the old <TT>CookieLog</TT> directive, but this should be upgraded to the above <TT>CustomLog</TT> directive. -<H2>Directives</H2> +<H2>2-digit or 4-digit dates for cookies?</H2> -<UL> -<LI><A HREF="#cookieexpires">CookieExpires</A> -<LI><A HREF="#cookiename">CookieName</A> -<LI><A HREF="#cookietracking">CookieTracking</A> -</UL> +(the following is from message +<022701bda43d$9d32bbb0$1201a8c0@christian.office.sane.com> in +the new-httpd archives) + +<P> + +<PRE> +From: "Christian Allen" <christian@sane.com> +Subject: Re: Apache Y2K bug in mod_usertrack.c +Date: Tue, 30 Jun 1998 11:41:56 -0400 + +Did some work with cookies and dug up some info that might be useful. + +True, Netscape claims that the correct format NOW is four digit dates, and +four digit dates do in fact work... for Netscape 4.x (Communicator), that +is. However, 3.x and below do NOT accept them. It seems that Netscape +originally had a 2-digit standard, and then with all of the Y2K hype and +probably a few complaints, changed to a four digit date for Communicator. +Fortunately, 4.x also understands the 2-digit format, and so the best way to +ensure that your expiration date is legible to the client's browser is to +use 2-digit dates. + +However, this does not limit expiration dates to the year 2000; if you use +an expiration year of "13", for example, it is interpreted as 2013, NOT +1913! In fact, you can use an expiration year of up to "37", and it will be +understood as "2037" by both MSIE and Netscape versions 3.x and up (not sure +about versions previous to those). Not sure why Netscape used that +particular year as its cut-off point, but my guess is that it was in respect +to UNIX's 2038 problem. Netscape/MSIE 4.x seem to be able to understand +2-digit years beyond that, at least until "50" for sure (I think they +understand up until about "70", but not for sure). + +Summary: Mozilla 3.x and up understands two digit dates up until "37" +(2037). Mozilla 4.x understands up until at least "50" (2050) in 2-digit +form, but also understands 4-digit years, which can probably reach up until +9999. Your best bet for sending a long-life cookie is to send it for some +time late in the year "37". +</PRE> <HR> -<H2><A NAME="cookieexpires">CookieExpires</A></H2> +<H2><A NAME="cookieexpires">CookieExpires</A> directive</H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -82,7 +147,8 @@ double quotes. <P>If this directive is not used, cookies last only for the current browser session.</P> -<H2><A NAME="cookiename">CookieName</A></H2> +<HR> +<H2><A NAME="cookiename">CookieName</A> directive</H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -122,7 +188,8 @@ you use a name containing unusual characters. Valid characters include A-Z, a-z, 0-9, "_", and "-". </P> -<H2><A NAME="cookietracking">CookieTracking</A></H2> +<hr> +<H2><A NAME="cookietracking">CookieTracking</A> directive</H2> <A HREF="directive-dict.html#Syntax" REL="Help" @@ -151,48 +218,7 @@ requests. This directive can be used to turn this behavior on or off on a per-server or per-directory basis. By default, compiling mod_usertrack will not activate cookies. -<HR> -<H2>2-digit or 4-digit dates for cookies?</H2> - -(the following is from message -<022701bda43d$9d32bbb0$1201a8c0@christian.office.sane.com> in -the new-httpd archives) - -<P> - -<PRE> -From: "Christian Allen" <christian@sane.com> -Subject: Re: Apache Y2K bug in mod_usertrack.c -Date: Tue, 30 Jun 1998 11:41:56 -0400 - -Did some work with cookies and dug up some info that might be useful. - -True, Netscape claims that the correct format NOW is four digit dates, and -four digit dates do in fact work... for Netscape 4.x (Communicator), that -is. However, 3.x and below do NOT accept them. It seems that Netscape -originally had a 2-digit standard, and then with all of the Y2K hype and -probably a few complaints, changed to a four digit date for Communicator. -Fortunately, 4.x also understands the 2-digit format, and so the best way to -ensure that your expiration date is legible to the client's browser is to -use 2-digit dates. - -However, this does not limit expiration dates to the year 2000; if you use -an expiration year of "13", for example, it is interpreted as 2013, NOT -1913! In fact, you can use an expiration year of up to "37", and it will be -understood as "2037" by both MSIE and Netscape versions 3.x and up (not sure -about versions previous to those). Not sure why Netscape used that -particular year as its cut-off point, but my guess is that it was in respect -to UNIX's 2038 problem. Netscape/MSIE 4.x seem to be able to understand -2-digit years beyond that, at least until "50" for sure (I think they -understand up until about "70", but not for sure). - -Summary: Mozilla 3.x and up understands two digit dates up until "37" -(2037). Mozilla 4.x understands up until at least "50" (2050) in 2-digit -form, but also understands 4-digit years, which can probably reach up until -9999. Your best bet for sending a long-life cookie is to send it for some -time late in the year "37". -</PRE> <!--#include virtual="footer.html" --> </BODY> diff --git a/docs/manual/mod/mod_vhost_alias.html b/docs/manual/mod/mod_vhost_alias.html index b402b6f8bc..8051209073 100644 --- a/docs/manual/mod/mod_vhost_alias.html +++ b/docs/manual/mod/mod_vhost_alias.html @@ -12,13 +12,7 @@ VLINK="#000080" ALINK="#FF0000" > -<DIV ALIGN="CENTER"> - <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]"> - <H3> - Apache HTTP Server Version 1.3 - </H3> -</DIV> - +<!--#include virtual="header.html" --> <H1 ALIGN="CENTER">Module mod_vhost_alias</H1> <P> |