Explanation: This is due to the fact how WebKit implements session support and how IIS handles redirects (HTTP 303). When new session is created, WebKit sets cookie _SID_ and pass it along with response (which happened to be a redirect). But unfortunately, IIS don't pass the redirect to browser. It does "internal redirect" and goes for the url specified in it. While doing this the _SID_ cookie is lost and WebKit starts another new session as it doesn't see the SID.


Does it matter what response code you use? I know Apache handles redirects differently depending on the response code. IE also has weirdness when you redirect and set a cookie.

I think so. IIS handles HTTP 303 only probably.


An useful fix to WebKit might be to capture the redirect, and if you are also setting a cookie then you redirect via Javascript or meta-refresh tag or something.

That's a good idea indeed!





------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to