There is one common method used to avoid this that is pretty
reliable.
1. http://example.org/1.php submits to http://example.org/2.php
2. http://example.org/2.php processes the form, then uses a
Location header to redirect to http://example.org/3.php. For
example:
header("Location: http://example.org/3.php";);
>From the user's perspective, there are only two URLs involved,
http://example.org/1.php and http://example.org/3.php. Clicking back
from 3.php brings the user to 1.php and clicking forward simply
brings the user to 3.php. It is impossible without clicking the
submit button again to execute 2.php again.
Thus, 2.php does not display anything but just processes the form and
redirects the user to the appropriate URL.
That's one technique, anyway.
Chris
--- David H <[EMAIL PROTECTED]> wrote:
> But what about updates to the database...? Is there
> away not to have the information send to the server at
> all?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
