That will work fine.
The other suggestion half-remembered by a previous poster is to do a
header("Location: ") after you process the post, so that their "Back"
button doesn't take them through the POST again.
However, a user who is intentionally playing with the submit, forward,
and back buttons
At 11:27 AM 7/13/2006, Michael B Allen wrote:
Let's say you have a "Buy" button that posts a form to a script that
inserts or increments the quantity of a record in a shopping cart
table. So you click "Buy" and then "Checkout". Now if you hit the Back
button it asks the user if they would like to
On Thu, 13 Jul 2006 14:41:21 -0400
Jim Moseby <[EMAIL PROTECTED]> wrote:
> >
> > Let's say you have a "Buy" button that posts a form to a script that
> > inserts or increments the quantity of a record in a shopping cart
> > table. So you click "Buy" and then "Checkout". Now if you hit the Back
>
Michael B Allen wrote:
> Let's say you have a "Buy" button that posts a form to a script that
> inserts or increments the quantity of a record in a shopping cart
> table. So you click "Buy" and then "Checkout". Now if you hit the Back
> button it asks the user if they would like to repost the form.
>
> Let's say you have a "Buy" button that posts a form to a script that
> inserts or increments the quantity of a record in a shopping cart
> table. So you click "Buy" and then "Checkout". Now if you hit the Back
> button it asks the user if they would like to repost the form. If you
> click "Ok"
Let's say you have a "Buy" button that posts a form to a script that
inserts or increments the quantity of a record in a shopping cart
table. So you click "Buy" and then "Checkout". Now if you hit the Back
button it asks the user if they would like to repost the form. If you
click "Ok" the db scrip
6 matches
Mail list logo
