Re^4: page expired message

Thank you, that is not the answer I was hoping for, but, unfortunately it is the one I expected.

Just so I am clear - the reason this is happinging is because I am posting to index.cgi and index.cgi is printing out a web page. To stop it from happening, I would need to post to index.cgi and have it redirect to a web page of some kind?

Another big question is why does this only happen with one client - I have personally never seen it and the majority of the other people I have using the site have only sporatically seen it.

Thank you for all your insight!

Comment on Re^4: page expired message

Replies are listed 'Best First'.
Re^5: page expired message by Tuppence (Pilgrim) on Jan 03, 2005 at 21:34 UTC
Further clarification here. The problem is that you are displaying a web page directly as a result of a POST - i.e. one request. This means, for instance, that if index.cgi, upon seeing the POST, handles the POST, then redirects to index.cgi with enough command line parameters to be able to give the user useful feedback, then everything will work correctly. Said another way, it doesn't matter who you redirect to - it can even be yourself - as long as handling the POST and displaying the web page are 2 seperate web requests. I would guess that all of your other clients have "dont show me this again" checked the first time it happens, and so never see it after that.	[reply]
Re^6: page expired message by Hammy (Scribe) on Jan 04, 2005 at 03:00 UTC
Thanks, conceptually everything you said makes sense, but what I have found out is this only happens when my site was in a frame (I only found that out after hours of testing). So if I run the index script outside of a frame, I do not get the page expired, If I put it in a frame, and I am using XP sp1, I get the message. If I am using XP sp2, I do not get the message (either in or out of frame). This is very strange. I am curious as to why XP sp2 fixes it (never version of IE as well (6.028 vs 6.029)	[reply]