Mystery Cache?

[ScaryBinary]

Hey all,

I'm having a really weird problem with an ASP application on our company server. This website stores user names and allows the users to query a database. When a user logs out, his "session" should be cleared to free up server resources.

The problem is that after the user logs out (and his session stuff has been killed), he can click the back button and return to the previous page, which displays all his info as if he never logged out! But when the Refresh button is clicked, the page is correctly updated and the user is redirected to the login page.

I thought this had something to do with the cache, but I've tried everything to get the page to refresh properly when the user clicks the back button - we even disabled and dumped the cache on our proxy server but still no luck. I've made sure that I set my browser up to check the page everytime it's requested, and I cleared the cache on my machine. I've added code in the ASP to immediately expire the page and prevent the proxy server from caching it.

So I am left with two questions:

Why does the page refresh properly when the Refresh button is clicked, but not when it is displayed after clicking the Back button?

Where the heck is the page coming from before it is refreshed, if all the caching is turned off? It doesn't appear to be coming from the client machine or the proxy server. And if it were really the true-blue page, wouldn't it be refreshed when it is called after clicking the Back button?

Thanks for any help, this is driving me crazy!

[BipolarBill]

The page is stored in RAM. There's not a lot you can do about that. It may help to set IE options so that page updating happens "Every visit to the page".

[ScaryBinary]

After messing around with my cache, I discovered some more interesting stuff....

In my ASP I tell the browser to expire the page immediately. I thought this would keep the page from being cached, but it turns out the page is still cached - but it's cached with an expiration date that is earlier than the current date. So the next time the browser checks the cache for that page, it should see that it's expired and go to the server for the latest page, right?

Wrong. For some reason, it still seems to load the cached page, even though (a) the page is expired in the cache, (b) I've set IE to check the site for new pages on every visit, and (c) the page is actually an ASP, not HTML, so it should be different every time it's loaded anyway.

I discovered that if I use my logout feature, then delete the exipired cached page from my Temporary Internet Files directory, then hit the back button to return to that page, the latest page is displayed as intended since it can't find the cached one.

Does anybody have any clue as to why IE insists on loading the cahced page even though it's expired?!?
:confused:

[SproutStrategies]

Did you ever find a solution to the mystery cache problem you were having? We built an application using Ruby on Rails and are having a similar problem with a group of users at a large company that is using a proxy server. When people access the application outside of that company, the site works just fine. But when they are on the company's network, we experience a cache problem like the one you had. If you have some suggestions, that would be great.

[algogocom]

So sorry to hear that.:-(Maybe you can ask the technician for the help.
Wish you have a good luck and have a nice weekend!
Rgds,
http://www.algogo.com

[Shoreguy]

So sorry to hear that.:-(Maybe you can ask the technician for the help.
Wish you have a good luck and have a nice weekend!
Rgds,
http://www.algogo.com


Spammers getting inventive :eek:

[Baddog]

Maybe you can ask the technician for the help.


:rolleyes: :D