Robert Collins wrote on 2010-11-19:
> What happens in browsers where we try to set both, once with and without the . ?
>
> If they silently ignore the non-leading dot one, it seems like a win.
Here are some experimental results.
When a request for example.com results in the response:
Lynx (2.8.8dev.2) will (if the user says "yes" to the cookie prompts)
send the cookie in requests for example.com but not in requests to
www.example.com.
When a request for www.example.com results in the same response, Lynx
will send the cookie in requests for www.example.com but not in requests
to example.com.
Therefore, we can't get Lynx to set a session cookie on launchpad.net
that will also be sent in requests to *.launchpad.net (and vice versa).
Robert Collins wrote on 2010-11-19:
> What happens in browsers where we try to set both, once with and without the . ?
>
> If they silently ignore the non-leading dot one, it seems like a win.
Here are some experimental results.
When a request for example.com results in the response:
HTTP/1.1 200 OK
content-type: text/plain
set-cookie: session=0; domain=.example.com
set-cookie: session=0; domain=example.com
Hello, there.
Lynx (2.8.8dev.2) will (if the user says "yes" to the cookie prompts)
send the cookie in requests for example.com but not in requests to
www.example.com.
When a request for www.example.com results in the same response, Lynx
will send the cookie in requests for www.example.com but not in requests
to example.com.
Therefore, we can't get Lynx to set a session cookie on launchpad.net
that will also be sent in requests to *.launchpad.net (and vice versa).