Re: Meaning of warning \"The cookie could not be set\"?
Cookies can be assigned to individual machines or to an entire Internet domain. The only restrictions on this value is that it must contain at least two dots for the normal top-level domains, e.g.
.myserver.com not myserver.com
or three dots for the "extended" domains e.g.
.myserver.ny.us not myserver.ny.us
The following is an extract from the Cookie spec in RFC 2109:
4.3.2 Rejecting Cookies
To prevent possible security or privacy violations, a user agent rejects a cookie i.e. shall not store its information, if any of the following are true:
* The value for the Domain attribute contains no embedded dots or does not start with a dot.
* The value for the Path attribute is not a prefix of the request-URI.
* The value for the request-host does not domain-match the Domain attribute.
* The request-host is a FQDN (not IP address) and has the form HD, where D is the value of
the Domain attribute, and is a string that contains one or more dots.
In our case it is the first rule that is being being broken. By way of example, look at this cookie entry in a SilkPerformer record.log file:
WebCookieSet("LastUserName=ISAPMOA; domain=segue.com; path=/servlet/QuoteServlet; expires=Sun, 04 Mar 2012 14:19:39 GMT", "http://segue/servlet/QuoteServlet");
Note that there is no dot "." before the value for the domain entry "segue.com" - this should read domain=.segue.com