I assume it's because HN sends the Set-Cookie header as part of an HTTP 302 redirect and expects the cookie to appear in the redirected request. Apparently this

I assume it's because HN sends the Set-Cookie header as part of an HTTP 302 redirect and expects the cookie to appear in the redirected request. Apparently this is against the HTTP spec, and won't work in certain browsers: http://www.persistall.com/archive/2008/01/25/cookies--redirects--nightmares.aspx http://www.persistall.com/archive/2008/01/25/cookies--redire...