Blocking back button to login page

ldd76

Hi,

I am using PHP4 with Mysql and IIS5.

After user login to my website, he can navigate around it with the back and forward buton on the browser.

I want to block the back button event to the login page. That is the user must click on the logout button to successfully go back to the login page.

Does anyone knows how I can ahieve this?

Thanks a million.
ldd

SpanKie

Depending on how you are processing the login, you can setup a test condition on the login page if the session is already started or the person is already logged in, redirect them to another page.

Just a though.

ldd76

I did what u mentioned with the isset() condition with $_SESSION command when registering seession variables but doesn't work.

for example,

User login in at pageA which calls a script to process the id and password. If all is well he gets redirected to PageB and from there he carry on. If the user press the back button while he is in
PageB, he will still be redirected to Page B and cannot go back to the login page(PageA). He can only do this if he click on the LOgout button.

Does anyone knows how to do this?

laserlight

I think it is possible to use meta tags to do this, something about cache-control.

It might be browser dependent though.

nemonoman

See this info.

http://www.phpbuilder.com/board/showthread.php?s=&postid=10408359#post10408359

Another possiblitiy would be to store a 'loggedin' cookie after a successful login.

In the script to your loggin page, you check to see if the user is loggedin:

if($_COOKIE['loggedin']{
location("http://someothersite.com")
}
else{
location("http://thissite.com/loginpage.php");
}

ldd76

But I don't use cookies....

The thing is how do I check that the login user in Page B had pressed the Back button that trys to access the login page(Page A).

nemonoman

The thing is, you have to use something that is independent of the page. Either you have to write a record to the database and check it, or you have to write a cookie and check that.

Using a cookie is probably best because you can check the cookie with a javascript script that is part of the page itself.

I can tell you don't like these answers, as there is some work and learning involved. You are trying to control the behavior of the webpage in ways that aren't inherent in the browser's behavior. To do this, you will have to write some code of your own.

Good luck.