"Page has expired" - again

[Mikael Andreasen]

Hi all,

I realize this subject has been brought up over and over, but I have
yet to find a suitable solution to the problem.

The problem:
When performing a POST, then navigating away from the page, then
pressing the Back button, IE6 presents the "Warning: Page has expired"
page instead of showing a cached version of the page.

The issue is covered in the following KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;319792
The article says the issue was corrected in Service Pack 1, but that
doesn't seem to be the case (I'm using 6.0 on XP Pro with all SPs and
hotfixes).

This problem is very relevant to an ASP.NET project I'm working on. It
is possible for me to make minor changes to the pages, but nothing
major like converting POST to GET etc. I use .NET's SmartNavigation
feature, but it doesn't seem to make any difference.

Any help or suggestions would be highly appreciated.
Thanks in advance!

/Mikael Andreasen

 

[Gregory H]

I have that problem as well...and I have all the updates. I believe that
this is a security issue directly related to the website's individual
security settings for the page.

All you need to do is to refresh the page...press F5, then press Enter.
That * Should * reload the page.

Gregory

 

[Guest]

Mikael,
This sounds like a scripting issue on the site. When using
cookies for login sessions, they are set to expire. If you
navigate away from the page they usually expire
immediately. That would explain why it doesn't display the
cached version (it's expired and wants an update). If the
cookie is expired, then the id & pw is expired as well -
thereby displaying that message.

As for the POST & GET conversions, this should probably be
done by downloading the file in question, changing the
commands on the local machine, then uploading the file to
the host.

Hope this helps,

Sean Reeves
(e-mail address removed)

 

[Mikael Andreasen]

Thank you for your reply.

I'm aware that reloading the page will cause the page to
show up, but I really need a way to make the page show up
without having to reload.

What makes you think this has to do with security
settings? Other browsers do not have this behavior, only
IE6 as far as I know.

That said, I'm willing to try anything that might resolve
the problem - do you have any idea what server settings
may help?

Thanks in advance,
Mikael Andreasen

 

[Mikael Andreasen]

Thank you for your reply, Sean

I do not think it's a scripting issue:
1) The web site has anonymous access and the only cookie
used (not login related) has a 1 year expiration date.
2) Other browsers (Netscape, Mozilla) do not have this
behavior.

I still think it's an IE6 specific bug - as numerous older
posts in this groups also suggest - but unfortunately my
client is on my back to resolve the issue, MS bug or not.

The reason converting POST to GET isn't feasible is that
I'm using .NET's intrinsic PostBack feature for all
functionality on the site. Changing this would require
changing thousands of lines of code.

Thank you for your suggestions, though.