Re: [Webware-discuss] Session expiration problem

2006-09-06 Thread Christoph Zwerschke
sophana a écrit: > Is your fix available in the 0.9.2 beta? I'd like to test it... The expired sessions fix has been added after the beta release, so you need to get it from the SVN. You can simply replace Application.py and HTTPExceptions.py in the WebKit folder from here: http://svn.w4py.org/

Re: [Webware-discuss] Session expiration problem

2006-09-06 Thread sophana
Christoph Zwerschke a écrit : I will also try to reimplement returning an error page for expired sessions if IgnoreInvalidSession=False (the default is True). Maybe instead of sending an error page, we should simply send a 408 Request Timeout error? I have fixed it that wa

Re: [Webware-discuss] Session expiration problem

2006-08-30 Thread Christoph Zwerschke
> I will also try to reimplement returning an error page for expired > sessions if IgnoreInvalidSession=False (the default is True). Maybe > instead of sending an error page, we should simply send a 408 Request > Timeout error? I have fixed it that way now, but sending "401 Session Expired" ins

Re: [Webware-discuss] Session expiration problem

2006-08-30 Thread Christoph Zwerschke
> In previous versions of webware (0.8.1), when a session expires the > method Application.handleInvalidSession() was called, which basically > removes the _SID_ reference so the browser will stop requesting an > invalid session, and marks request._sessionExpired. So, I could ask > for the var

[Webware-discuss] Session expiration problem

2006-08-30 Thread niurkapm
Hello, I’m developing a web site using python 2.4.3 and Webware 0.9.1.   I have a problem to know when a session is actually expired and is not a brand new session because the user just entered to the site.   In previous versions of webware (0.8.1), when a session expires the method A