On 2 Aug 2009, at 23:04, Sanford Whiteman wrote:
I just thought that it *might* be possible that the browser has the
cookie in memory (and accessible via JS) on the page that has the
initial "set-cookie" http header, but doesn't keep it in memory on
any subsequent pages.
You're not so wrong about this. The browser gets the original HTTP
header (in serialized form) no matter what. But generic browsers are
under no obligation to keep it around for you to query. From some HTTP
clients, say cURL, you can definitely read the header even if the
client isn't storing and resending cookies. Standard XMLHTTP
implementations should let you read them out, too (see
getAllResponseHeaders).
It's good to know know I'm not "so" wrong, but it would be nice to not
be wrong at all!
Thanks for the clarification,
Michal.
