I hope you are not too new to PHP that you are fully aware of the security> I am new to PHP
> To get to that, the user has to go through a credit card verification
> script getpaid.php, which contacts the bank and confirms that the card
> has available funds
implications of your work with this sort of application. I'm not trying to
be patronising, just pointing out that application security generally
requires experience, because you should be aware of all the things that
can go wrong or ways in which data can be faked. I hope that's not an
The usual solution is to issue a header containing a 301 redirect to a new> The problem is that after the user gets the pin from display.php and
> refresh the page, the script will run again and as the value that has
> been sold first time has already been deleted, it will take the next pin
> number in the database and display it to the user again. That is
> something I don't want to happen. I want the user to get the same pin
> number that it got the first time every time they refresh the page.
page immediately the post transaction has been verified and completed. The
user won't even know that they're being redirected, but it guarantees that
pressing refresh won't repeat the transaction.
I don't have a working example to hand, but I hope this gives you enough
to go on.
Martin Lucas-Smith [url]www.geog.cam.ac.uk/~mvl22[/url]
Senior Computing Technician (Web Technician)
Department of Geography, University of Cambridge (01223 3)33390
& Webmaster, SPRI
Scott Polar Research Institute, University of Cambridge