Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.
 
PerlMonks  

Re^3: page expired message

by Tuppence (Pilgrim)
on Jan 03, 2005 at 19:14 UTC ( [id://419023]=note: print w/replies, xml ) Need Help??


in reply to Re^2: page expired message
in thread page expired message

As this is a client-side message, you will be able to do nothing on the server to fix it aside from fixing your page flow and not displaying pages directly from POSTed form content.

FYI, the mozilla version of this error is the pop-up box that says something about clicking OK will re-submit this form possibly causing an action to be repeated

Replies are listed 'Best First'.
Re^4: page expired message
by Hammy (Scribe) on Jan 03, 2005 at 20:09 UTC
    HUGE ADDITION TO THIS ISSUE::
    This only happens when my site is put inside a frame (frame from my own site). It also only happens on XP service pack 1. Not sure if this adds anything, but I just thought I would mention it. Thanks you again, very much.
Re^4: page expired message
by Hammy (Scribe) on Jan 03, 2005 at 19:34 UTC
    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!

      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.

        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)

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://419023]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (7)
As of 2024-04-23 20:52 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found