vincent wrote:
Cookie can be set to be returned only to one domain, but they can equally simply be set to be sent to any domain.
That's why you should never use cookies with obvious names.
Simple pre-pending your site's name usually does the trick,
so your 'id' cookie would become something like 'your_site_id'
Are you sure that they can be set to any domain? I was looking into this more, and I found the Netscape Cookie Specification (http://www.netscape.com/newsref/std/cookie_spec.html) and it states the following:
"Only hosts within the specified domain can set a cookie for a domain and domains must have at least two (2) or three (3) periods in them to prevent domains of the form: ".com", ".edu", and "va.us". Any domain that fails within one of the seven special top level domains listed below only require two periods. Any other domain requires at least three. The seven special top level domains are: "COM", "EDU", "NET", "ORG", "GOV", "MIL", and "INT".
The default value of domain is the host name of the server which generated the cookie response."
This would lead me to believe that in order for the doubleclick cookie to get to my server, something very odd must have happened either on my server or with the client's web browser. This might just be an isolated incedent, but I'd like to find out what happened.
Jason Bauer
jbauer@mtu.edu
Michigan Tech Fund
Web Site Coordinator