RPG.  I carry the order number from page to page and use that to make sure that
an order is not submitted twice.  this is an internal web site used only by
employees.  the main thing they do not want is for people to be able to hit the
back button after the order has completed to see the customer's credit card
number in case the employee using the browser does not close it after the order
has been completed.  what I have done for now is prevent them from going back to
that page at all and placed an edit button on the payment confirmation screen
that will take them back to the credit card entry screen if changes are needed
before submitting the order.

----- Original Message ----- 
From: "Sarah Poger Gladstone" <listmember@xxxxxxxxxxxxxx>
To: "Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
Sent: Thursday, January 26, 2006 9:40 AM
Subject: Re: [WEB400] Prevent Browser From Going Back


Joe-

What server-side language are you using to handle the order? Assuming
you have some sort of session tied to the user, you can place
"orderstatus" and a "requested_action" variables in the session. Then
no matter what page the user is on ( and no matter how they got there
ie using the back button) your server side program can validate that
the "requested_action" is appropriate based on the current
"orderstatus"

HTH,
Sarah


On 1/25/06, Jeffrey Lee <jeff@xxxxxxxxxxx> wrote:
> On the page that you do not want them to go back to you could put an onload
> event that would set the value of all of the fields.
>
> < body onLoad="return empty()" >
> <!--
> <!--
> function empty()
> {
>
> document.CCForm.CCNumber.value=""
> document.CCForm.CCExDate.value=""
>
> return true
> }
> //-->
> // -->
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.