Re: CGI::Session Expiration Woes

The second problem, related to the back button, occurs because the browser re-post the old values to the login page, causing the user to re-authenticate. I read an article (don't remember where) that suggests the addition of a third page in the "login" sequence, to avoid this "feature" of some browsers...

-DBC

Comment on Re: CGI::Session Expiration Woes

Replies are listed 'Best First'.
Re^2: CGI::Session Expiration Woes by Anonymous Monk on Aug 11, 2004 at 20:11 UTC
that's not quite what happens danielcid. They time out, they log in and go to the "login.cgi". Upon clicking the page they timed out on, it goes to "login.html". But if the user browses back to the "login.cgi" and clicks that link again, the user can navigate to the page. so it is more of a stutter step then a reposting problem, because I'm using mozilla and if i need to repost, it would prompt me to do so. amt.	[reply]

Replies are listed 'Best First'.

Re^2: CGI::Session Expiration Woes
by Anonymous Monk on Aug 11, 2004 at 20:11 UTC

that's not quite what happens danielcid. They time out, they log in and go to the "login.cgi". Upon clicking the page they timed out on, it goes to "login.html". But if the user browses back to the "login.cgi" and clicks that link again, the user can navigate to the page. so it is more of a stutter step then a reposting problem, because I'm using mozilla and if i need to repost, it would prompt me to do so. amt.

[reply]