Duplicate Entries on browser refresh

Hi

Has anyone found a solution to the problem of
duplicate entries when the browser refresh/reload
button is pressed immediately following submission of
a comment/reply in RT?

I understand this problem is not specific to RT and
that it relates to HTTP POST processing but was
wondering if anyone had found a neat
solution/workaround?

Thanks in advance

To help you stay safe and secure online, we’ve developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

brian mccabe wrote:

Hi

Has anyone found a solution to the problem of
duplicate entries when the browser refresh/reload
button is pressed immediately following submission of
a comment/reply in RT?

I understand this problem is not specific to RT and
that it relates to HTTP POST processing but was
wondering if anyone had found a neat
solution/workaround?

A more subtle variation of this is if you use Firefox’s SessionSaver, or
SAFT for Safari. If you update a ticket as the last thing before you
quit the browser, then you get that same update again when you restart,
sometimes.

Some kind of ‘one-time key’ in the submitted form that gets checked off
as used by the receiving page would do it, but it sounds like it would
be a fiddle to retrofit it.

Howie