From: patrikj
Date: Mon, 11 Mar 2002 12:01:25 +0000 (+0000)
Subject: Cleaned up so that it validates
X-Git-Tag: CHANGES~142
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9e6e3782621ec99ffcf48a4585f0beba0d6cb930;p=apache
Cleaned up so that it validates
to
to
and so on...
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93838 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_usertrack.xml b/docs/manual/mod/mod_usertrack.xml
index ab6c0e901a..078eb8f655 100755
--- a/docs/manual/mod/mod_usertrack.xml
+++ b/docs/manual/mod/mod_usertrack.xml
@@ -14,9 +14,6 @@
Known as mod_cookies prior to Apache 1.3.
-
- Summary
-
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
@@ -30,20 +27,20 @@
Logging
Previously, the cookies module (now the user tracking
- module) did its own logging, using the CookieLog
+ module) did its own logging, using the CookieLog
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 multiple log files. The cookie itself is logged by
- using the text %{cookie}n in the log file format. For
+ using the text %{cookie}n
in the log file format. For
example:
CustomLog logs/clickstream "%{cookie}n %r %t"
For backward compatibility the configurable log module
- implements the old CookieLog directive, but this
- should be upgraded to the above CustomLog directive.
+ implements the old CookieLog directive, but this
+ should be upgraded to the above CustomLog directive.
@@ -51,7 +48,7 @@ CustomLog logs/clickstream "%{cookie}n %r %t"
(the following is from message
<022701bda43d$9d32bbb0$1201a8c0@christian.office.sane.com>
- in the new-httpd archives)
+ in the new-httpd archives)
From: "Christian Allen" <christian@sane.com>
Subject: Re: Apache Y2K bug in mod_usertrack.c
@@ -84,12 +81,13 @@ 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".
-
+
CookieDomain
-CookieDomain domain
+controls the setting of the domain to which the tracking cookie applies.
+CookieDomain domain
None
server config
@@ -97,8 +95,6 @@ time late in the year "37".
directory
.htaccess
-controls the setting of the domain to which
- the tracking cookie applies.
@@ -106,8 +102,8 @@ time late in the year "37".
the tracking cookie applies. If not present, no domain is
included in the cookie header field.
- The domain string must begin with a dot, and
- must include at least one embedded dot. That is,
+
The domain string must begin with a dot, and
+ must include at least one embedded dot. That is,
".foo.com" is legal, but "foo.bar.com" and ".com" are not.
@@ -165,8 +161,9 @@ time late in the year "37".
CookieStyle
+Controls the format of the cookie header field
CookieStyle
- Netscape|Cookie|Cookie2|RFC2109|RFC2965
+ Netscape|Cookie|Cookie2|RFC2109|RFC2965
server config
@@ -174,22 +171,20 @@ time late in the year "37".
directory
.htaccess
-Controls the format of the cookie header
- field
This directive controls the format of the cookie header
field. The three formats allowed are:
- - Netscape, which is the original but now deprecated
+
- Netscape, which is the original but now deprecated
syntax. This is the default, and the syntax Apache has
historically used.
- - Cookie or RFC2109, which is the syntax that
+
- Cookie or RFC2109, which is the syntax that
superseded the Netscape syntax.
- - Cookie2 or RFC2965, which is the most
+
- Cookie2 or RFC2965, which is the most
current cookie syntax.