Same here: I can log into edge.launchpad.net and code.launchpad.net, but not into launchpad.net. The headers are slightly different for each:
launchpad.net: Set-Cookie: lp=XXX; Domain=.launchpad.net; expires=Thu, 30 Jul 2009 22:54:10 GMT; Path=/; secure;
edge.launchpad.net: Set-Cookie: edge=XXX; Domain=.launchpad.net; expires=Thu, 30 Jul 2009 22:54:47 GMT; Path=/; secure;
code.launchpad.net Set-Cookie: lp=XXX; Domain=.launchpad.net; expires=Thu, 30 Jul 2009 22:56:12 GMT; Path=/; secure;
But from what I can see this is actually a bug in either w3m or the RFC (or both). I don't see any reason why it should be okay for https://code.launchpad.net/ to set cookies for .launchpad.net, but not https://launchpad.net/ itself!
Same here: I can log into edge.launchpad.net and code.launchpad.net, but not into launchpad.net. The headers are slightly different for each:
launchpad.net: .launchpad. net; expires=Thu, 30 Jul 2009 22:54:10 GMT; Path=/; secure;
Set-Cookie: lp=XXX; Domain=
edge.launchpad.net: .launchpad. net; expires=Thu, 30 Jul 2009 22:54:47 GMT; Path=/; secure;
Set-Cookie: edge=XXX; Domain=
code.launchpad.net .launchpad. net; expires=Thu, 30 Jul 2009 22:56:12 GMT; Path=/; secure;
Set-Cookie: lp=XXX; Domain=
But from what I can see this is actually a bug in either w3m or the RFC (or both). I don't see any reason why it should be okay for https:/ /code.launchpad .net/ to set cookies for .launchpad.net, but not https:/ /launchpad. net/ itself!