On Mon, 2004-12-13 at 18:58 -0500, Ingo Weiss wrote:
> print $query->redirect('http://somewhere.else/in/the/world');
>
> In the above example, the document that was originally requested does
> never make it to the client, right?
The client should receive the entire document that your script sends
> redirect (302 response) after handling the form
That's interesting! Thanks! I took a look at the documentation:
print $query->redirect('http://somewhere.else/in/the/world');
Is this how it is done?
In the above example, the document that was originally requested does
never make it to the cli
Ingo Weiss wrote:
Hi,
this must be a common problem and I was wondering what commonly used
strategies to solve it are:
How can I avoid that a user re-sends a POST form when hitting the reload
button on a result page?
The browser typically warns you when you want to do that but I was
wondering wheth
> "Ingo" == Ingo Weiss <[EMAIL PROTECTED]> writes:
Ingo> this must be a common problem and I was wondering what commonly used
Ingo> strategies to solve it are:
Ingo> How can I avoid that a user re-sends a POST form when hitting the reload
Ingo> button on a result page?
Ingo> The browser typ
Ingo Weiss wrote:
> Hi,
>
> this must be a common problem and I was wondering what commonly used
> strategies to solve it are:
>
> How can I avoid that a user re-sends a POST form when hitting the
> reload button on a result page?
You can't. If the transaction is not repeatable, you need to have
Hi,
this must be a common problem and I was wondering what commonly used
strategies to solve it are:
How can I avoid that a user re-sends a POST form when hitting the reload
button on a result page?
The browser typically warns you when you want to do that but I was
wondering whether there is an
> I'm no CGI expert, but my best guess is that you are not going to be able to
> stop the user from resending the data
>
[snip out a technique to assist in ignoring repeat data]
This deserves to be drilled into every beginning CGI programmers brain:
You cannot PREVENT the client from doing ANYTH
I'm no CGI expert, but my best guess is that you are not going to be able to
stop the user from resending the data, so you are going to have to make sure
you ignore the resent data. I would do this by generating a random number in
a hidden input field when creating the form. Then you can check that
Hi,
this must be a common problem and I was wondering what commonly used
strategies to solve it are:
How can I avoid that a user re-sends a POST form when hitting the reload
button on a result page?
The browser typically warns you when you want to do that but I was
wondering whether there is an
