 |  |  |  |  |  |  |  |
Creating a Robust Logout System
 |
When someone logs out of our site, I want the previous page to not be accessible (or any of the other pages.)
So far, when a user clicks the logout button on our site, I do the following:
1) I write to a file
2) erase the session cookie
3) disable the back button.
When each page loads on our site, it checks to make sure the login file has the correct variable, checks to see if the session cookie has a value. The session cookie is checked by javascript upon page loading, the login file is checked on the server.
Everything works but when someone hits the back button, there is enough of a delay where the page can still be viewed before the javascript redirects it.
Is there a better way to do this so that when someone clicks back, the information is no longer there at all?
Thanks!
So far, when a user clicks the logout button on our site, I do the following:
1) I write to a file
2) erase the session cookie
3) disable the back button.
When each page loads on our site, it checks to make sure the login file has the correct variable, checks to see if the session cookie has a value. The session cookie is checked by javascript upon page loading, the login file is checked on the server.
Everything works but when someone hits the back button, there is enough of a delay where the page can still be viewed before the javascript redirects it.
Is there a better way to do this so that when someone clicks back, the information is no longer there at all?
Thanks!
•
•
Join Date: Jul 2004
Posts: 494
Reputation: 
Solved Threads: 21
Posting Pro in Training
Don't break the back button. The back button can take you back past your own page to pages visited before, so breaking it annoys people.
You should probably do the cookie checking through Perl, not Javascript. That way, when your user hits the back button they either get a cached version of the page (they were authorized to view it in the first place), or they get a "You have been logged out" message. If you're really worried about cached pages like that, you can add a custom header that says the page expired sometime in the past. (1969 would be a good year.)
You should probably do the cookie checking through Perl, not Javascript. That way, when your user hits the back button they either get a cached version of the page (they were authorized to view it in the first place), or they get a "You have been logged out" message. If you're really worried about cached pages like that, you can add a custom header that says the page expired sometime in the past. (1969 would be a good year.)
www.uncreativelabs.net
Old computers are getting to be a lost art. Here at Uncreative Labs, we still enjoy using the old computers. Sometimes we want to see how far a particular system can go, other times we use a stock system to remind ourselves of what we once had.
Old computers are getting to be a lost art. Here at Uncreative Labs, we still enjoy using the old computers. Sometimes we want to see how far a particular system can go, other times we use a stock system to remind ourselves of what we once had.
Ok, getting "this page has expired" to come up whenever they try to go back to one of our pages is exactly what I want to do. Now how do I actually do it?
•
•
Join Date: Jul 2004
Posts: 494
Reputation:
Solved Threads: 21
Posting Pro in Training
Use the CGI module.
http://search.cpan.org/dist/CGI.pm/CGI.pm#HTTP_COOKIES
(For your convience, the link will show the HTTP cookies section first.)
http://search.cpan.org/dist/CGI.pm/CGI.pm#HTTP_COOKIES
(For your convience, the link will show the HTTP cookies section first.)
www.uncreativelabs.net
Old computers are getting to be a lost art. Here at Uncreative Labs, we still enjoy using the old computers. Sometimes we want to see how far a particular system can go, other times we use a stock system to remind ourselves of what we once had.
Old computers are getting to be a lost art. Here at Uncreative Labs, we still enjoy using the old computers. Sometimes we want to see how far a particular system can go, other times we use a stock system to remind ourselves of what we once had.
•
•
Join Date: Jun 2006
Posts: 263
Reputation:
Solved Threads: 1
Posting Whiz in Training
•
•
•
•
Originally Posted by Puckdropper 
If you're really worried about cached pages like that, you can add a custom header that says the page expired sometime in the past. (1969 would be a good year.)
See here: http://computer.howstuffworks.com/question75.htm
It usually best to use 00:00:01 Jan 1 1970 to make objects expire instantly. Just a helpful tip
.Steven.
The one question you should not ask when teaching a new language structure is "Do you understand?". Do you understand?
|
Similar Threads
- Chat system (ASP.NET)
- Chat system for students!! (Java)
- Chat system for students!! (VB.NET)
- System CPU overusage (Windows NT / 2000 / XP)
- would somebody buy this for me? (Troubleshooting Dead Machines)
Other Threads in the Perl Forum
- Previous Thread: Making global constants/Making constants global
- Next Thread: Get the location of the perl script
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Perl Posts
- Today's Posts
- Unanswered Threads
