Sub-domain cookies, sent in a parent domain request?

The leading dot in the domain value example.com" rel="nofollow">example.com means example.com" rel="nofollow">example.com and its subdomains. Without the leading dot, the cookie is only valid for this specific domain.

The leading dot in the domain value . Example.com means example.com and its subdomains. Without the leading dot, the cookie is only valid for this specific domain.

Note that when setting a cookie, domain values without a leading dot will be prepended with a dot. Only when the domain parameter is not set the user agent assumes the current domain for that cookie. So in this case, if http://example.com/ is requested, only the cookie for .

Example.com will be sent. But in case of http://foo. Example.com/, both cookies for .

Example.com and foo. Example.com will be sent. And in case of http://bla.foo.

Example.com, only the cookie for . Example.com will be sent.

No. It's the other way around: parent-domain cookies are sent in sub-domain HTTP requests.

The cookies of a subdomain only get sent if they were set with a domain with a leading dot on the level above it. So if example.com sets a cookie with domain ".example. Com" then it gets sent, otherwise not.

The other way around is more confusing, the cookie set in the top level domain should only get sent to subdomains if it has the leading dot but if you are using internet explorer it will also send it if it got sent without the leading dot (ref).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.