An Idea I have just had but not tested. To start:- Page1 - Input Form Page2 - Data Handling (i.e. processing the form) Page3 - Redirect handler.
So, User fills in form on Page1 then submits it. Page2 then processes this data and if it handles it correctly it simply sends a redirect (something like a Meta Refresh with time set to 0) to Page3 which then sends you onto the final page. By using a querystring variable and checking this in page2 you could probably get rid of Page3 and have its part handled in page2. I hope this makes sense. Cheers Lee ----- Original Message ----- From: "César Aracena" <[EMAIL PROTECTED]> To: "'Petre'" <[EMAIL PROTECTED]> Cc: "'php-general'" <[EMAIL PROTECTED]> Sent: Wednesday, July 31, 2002 7:06 PM Subject: RE: [PHP] Disabling Browser "BACK" button Well... you simple can't unless you take advantage from all the wonderful features of PHP like it's capability to know where the request comes from. Another interesting point would be to see if your program is made correctly, so your script(s) will handle just the right stuff. That is, if you point your form in Page1 to a Script in Page2, you should be pretty sure that it will handle the right stuff. After all the handling was done, you should be able to unset the variables in order *FORBID* the user to push the REFRESH or BACK buttons, submitting the data all over again. > -----Original Message----- > From: Petre [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 2:50 PM > To: César Aracena > Cc: php-general > Subject: Re: [PHP] Disabling Browser "BACK" button > > I hear you, but how do I know if the POST comes from a valid form > submit, or from a "back" ? I cannot simply unset the $_POST vars, as > that will prevent anything from being posted correctly, right? > > > César Aracena wrote: > > >I think that would be easy just by UNSETTING or emptying the variables > >that the form passed after they are processed. Do I make sence? > > > >César > > > >>-----Original Message----- > >>From: Petre [mailto:[EMAIL PROTECTED]] > >>Sent: Wednesday, July 31, 2002 2:43 PM > >>To: Martin Clifford > >>Cc: php-general > >>Subject: Re: [PHP] Disabling Browser "BACK" button > >> > >>Well, OK, then, How do you design the app NOT to allow the form to > >> > >POST > > > >>again when the user hits "BACK" > >> > >>Martin Clifford wrote: > >> > >>>There is never a way to disable back, forward, home, etc buttons. > >>> > >They > > > >>all have shortcuts that will ALWAYS work, so there's really no point. > >>Additionally, it's all nice and good that your site works fine without > >>using cookies, and don't take this offensively, but if the client > >> > >cannot > > > >>use the back button without getting mishapen results, then it doesn't > >>sound as if the site is designed very efficiently. > >> > >>>Just my opinion. > >>> > >>>Martin Clifford > >>>Homepage: http://www.completesource.net > >>>Developer's Forums: http://www.completesource.net/forums/ > >>> > >>> > >>>>>>Petre <[EMAIL PROTECTED]> 07/31/02 01:16PM >>> > >>>>>> > >>>HI > >>>Is there a way I can disable the client's browser back button, > >>> > >forcing > > > >>>them to use the navigation I built into the page? > >>>Ideally, when they try to press "BACK" on browser, a popup asking > >>> > >them > > > >>>to use the navigation instead would win first prize. > >>> > >>>The reason I'm asking is again to do with sessions, I have an app > >>>running 100% now without using cookies, but if the user hits BACK and > >>>ignores the expire warning, the app produces unwanted results ( adds > >>>form data again to the db etc.) > >>>Just want to patch the holes. > >>> > >>>Maybe write my own little browser that has no back button?? > >>> > >>> > >>> > >> > >> > >>-- > >>PHP General Mailing List (http://www.php.net/) > >>To unsubscribe, visit: http://www.php.net/unsub.php > >> > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
