[Seaside] Session handling
ted.wrinch at gmail.com
Tue Nov 15 23:22:43 UTC 2011
I've just picked up Seaside 3.1 and had a go at using the new session handling features. I like the way it's all been put together, so that the crawler handler will fallback to cookies for the normal case. But might I suggest that the cookie-if-supported handler might be the best fallback option here? And it might even make sense to make the crawler handler the default out-of-the-box handler, rather than the current field handler. That's the good. The bad is that:
1) I can't get the cookie-if-supported handler to drop the URL session field on my machine (running OSX and Chrome). Chrome indicates that the request header never has the seaside session cookie set (though it always has a cookie called aida9357=894862669 set for some reason).
2) If I switch to the cookie-only tracker the field URL goes away but I can't get any other than the start-up session to work (clicking on links fails).
Does anyone know what might be going on or where I might look to fix this?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside