At 17:17 28/04/2001 -0500, will trillich wrote:
>so i guess what you're saying is, some browsers look for
>a "redirect:" header and then charge off to the new location
>without handling any "set-cookie:" headers in the meantime?
Precisely. And some also don't report the cookie before the second page
after the redirect (presumably because they consider it to be the same
request). I think that behaviour only happens with permanent redirects though.
One thing that helps (often, not always) is to make sure that your
Set-Cookie header is sent before the Location header of the redirect.
_______________________________________________________________________
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
"Many people would sooner die than think. In fact, they do." - Bertrand
Russell
