On Nov 21, 2003, at 8:47 AM, Max Ischenko wrote:
I (and probably other) have struggled a nasty problem occurred when WebKit used as an application server behind a IIS. Here I'd like to give a simple solution for those interested and (may be) to be included in the next Webware release.

Problem description: When you put some data on your session object and redirects to another WebKit page you don't find the data. In fact, you could discover that you have another (brand new) session object!

Yes, when sessions act weird it's usually because of cookies.


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.


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.

--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org



-------------------------------------------------------
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