This directive controls the setting of the domain to which
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,
.example.com is legal, but www.example.com and
.com are not.

Most browsers in use today will not allow cookies to be set
for a two-part top level domain, such as .co.uk,
although such a domain ostensibly fulfills the requirements
above.
These domains are equivalent to top level domains such as
.com, and allowing such cookies may be a security
risk. Thus, if you are under a two-part top level domain, you
should still use your actual domain, as you would with any other top
level domain (for example .example.co.uk).

When used, this directive sets an expiry time on the cookie
generated by the usertrack module. The expiry-period
can be given either as a number of seconds, or in the format
such as "2 weeks 3 days 7 hours". Valid denominations are:
years, months, weeks, days, hours, minutes and seconds. If the expiry
time is in any format other than one number indicating the
number of seconds, it must be enclosed by double quotes.

If this directive is not used, cookies last only for the
current browser session.

This directive controls the format of the cookie header
field. The three formats allowed are:

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
superseded the Netscape syntax.

Cookie2 or RFC2965, which is the most
current cookie syntax.

Not all clients can understand all of these formats, but you
should use the newest one that is generally acceptable to your
users' browsers. At the time of writing, most browsers support all
three of these formats, with Cookie2 being the
preferred format.

When mod_usertrack is loaded, and
CookieTracking on is set, Apache will send a
user-tracking cookie for all new requests. This directive can
be used to turn this behavior on or off on a per-server or
per-directory basis. By default, enabling
mod_usertrack will not
activate cookies.

Notice:This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.