Showing signin after signout when we click on back button

hi,thanks for your reply but i dont want to add this
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetAllowResponseInBrowserHistory(false);

Going further, this is what Sandeep said:

When user login then take value in session but when user logout then remove session but when he/she again on listview page then check there session is not null if null then show there nis link display/visible true on Listview page.

That won't work most of the time.  In most browsers, when you come to a page by hitting the back button, the browser doesn't run the Javascript or do a postback.  So it doesn't matter whether you use Sandeep's code or anyone else's code.  If there's no postback, the code isn't going to run.

This comes up a lot.  Here's what's happening: 

Your browser caches the web pages it views.  This makes everything faster.  When a page loads, the browser only downloads and updates the items that have changed.  The rest comes from the browser's cache.  The problem with this is that, even after the user has logged out, the browser still has your pages cached, including the ViewState.  So the user can hit the back button or history and view the old pages.  He can also look in the temporary internet files folder and see things.

Furthermore, in many browsers, when you hit the back button, the browser simply reloads the prior page from its cache.  It doesn't execute the Javascript and it doesn't do a postback.  So it doesn't matter what your code looks like.  It doesn't matter what Javascript you put on the page.  The user can hit the back button and view the old page, just like it was when he left it.
That's what you're seeing.  The page said Logout before.  You redirected to a different page.  When they hit the back button, it should look the same as before, with Logout displayed.

You can't stop your user from hitting the back button.  The only thing you can do is prevent the browser from caching, which means there will be nothing to see when he hits the back button.  The easiest way to do this is to add this to each page in the OnLoad( ):

Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetAllowResponseInBrowserHistory(false);

Your performance will be slower because the browser won't cache your page.  It will reload everything on every post back.  But it will prevent the user from viewing the last page by hitting the back button.  He'll get a message that the page has expired. 

It's a tradeoff.  Your performance will be slower, but the user won't be able to navigate backwards.  You'll have to decide whether it's worth it.  

thanks for you reply

but i have linkbutton, images etc... on to the listview page that shows and depends upon user signin/signout.what about this.

When user login then take value in session 
but when user logout then remove session
but when he/she again on listview page then check there session is not null if null then show there
nis link display/visible true on Listview page.
There have a link Sign in that is visible only when session is null
else link is disapper by default value of Visible of link set False
true or false check at load time in page load condition.

hi, thanks for your reply

but i dont want like this mate.

if we signout the page on listview and comeback on listview page then it will show signin.

Listview page is not in authentication and will be see if user is signout.

when u click Signout then u use Session.Abandon() Method and on every page u check Session["user"]!=null
at page on Page load event of every page when u click back but than page call that web form pageload check session["user"]!=null
if yes then redirect on singin page.


Logout.aspx Page