CookieDomain

Specify a cookie domain name that's common to all of the servers providing Interchange content.

Synopsis

Scope

This directive is only available for use in the local (catalog.cfg) configuration file.  It will not affect any other website in any way.  This directive will not work in the global (interchange.cfg) configuration file. 

Description

This directive directive specifies a cookie domain name that's common to all of the servers providing Interchange content.

By default, the session ID cookie domain is set to the website's current hostname and domain name.  For example, if you access the website using "www.example.com", then the cookie domain name will be set to "www.example.com" as well.

Things get more complicated if you use more Interchange servers, in a non-transparent way, to provide content.  For example, if SSL content is served from "secure.example.com", then users would have one session and cookie for "www.example.com" and another separate session and cookie for "secure.example.com".  To fix this problem, we need to find part of the domain name that is common to all servers (".example.com", in our example)

The cookie specification mandates that the domain name must contain at least two dots.  The value of ".example.com" is valid, but "example.com", ".com" and "com" are all invalid.

Warning The cookie domain must be valid for the host.  For example, if your "host.domain" is "www.example.com then you will not be allowed to set the cookie domain to ".cursor.biz".

The CookieDomain directive accepts a space-separated list of cookie domains.  If more than one domain is specified then multiple "Set-Cookie:" HTTP headers will be generated - one for each of the specified domains.