Re: [OT] GET-then-redirect 'reload' behavior

2007-04-08 Thread Rashmi Rubdi
On 4/8/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: This issue has already been identified as "not an issue". If you read the original post, you'd see that I was, in fact, using redirects after non-cleanly-repeatable operations. :( Ok, I was guessing that there might probably be an HTTP F

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rashmi, Rashmi Rubdi wrote: > These 2 articles talk about how to properly prevent idempotent data > from being manipulated (deleted, saved etc) more than once. > > http://www.javaranch.com/journal/200603/frontman.html > > http://www.theserverside.co

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-07 Thread Rashmi Rubdi
These 2 articles talk about how to properly prevent idempotent data from being manipulated (deleted, saved etc) more than once. http://www.javaranch.com/journal/200603/frontman.html http://www.theserverside.com/tt/articles/article.tss?l=RedirectAfterPost I tested this on Tomcat 6.0.x, and found

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas, Andreas Prieß wrote: > I think the HTTP spec says that there should be _no_ change of status > performed on a GET request - GET should alwasy be repeatable without > danger. While I think you're right, and agree in general, my UI makes the m

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-07 Thread Andreas Prieß
Zitat der eMail vom 06.04.2007 um 12:41 Uhr: > I recently discovered that a redirect-after-GET does not offer this > protection. I have a link on one page that duplicates the current > record, then does a redirect to the "view record" page displaying the > new record. > Any other ideas or thoughts

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Len, Len Popp wrote: > That's not the behaviour I'm seeing with Firefox 1.5 (I haven't tried 2.0). So weird... I observed this the other day and it's not doing it anymore (i.e. it is working as I expected, without the re-GET). I have the same procedu

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-06 Thread Martin Gainty
destroy the original message without making a copy. Thank you. - Original Message - From: "Len Popp" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Friday, April 06, 2007 1:26 PM Subject: Re: [OT] GET-then-redirect 'reload' behavior That's

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-06 Thread Rashmi Rubdi
Me too. I tired this on Firefox 2.0.0.3 The only time it re-GETs or re-POSTs the original request is when HTTP Forward is used. If HTTP Redirect is used , it never re-GETs or re-POSTs the original request. -Rashmi On 4/6/07, Len Popp <[EMAIL PROTECTED]> wrote: That's not the behaviour I'm see

Re: [OT] GET-then-redirect 'reload' behavior

2007-04-06 Thread Len Popp
That's not the behaviour I'm seeing with Firefox 1.5 (I haven't tried 2.0). I have a page that responds to a GET with a 302 redirect. The browser then automatically GETs the redirect page, and the redirect URL is shown in the address bar, and if I reload the page it re-GETs the second page, not t

[OT] GET-then-redirect 'reload' behavior

2007-04-06 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I have many form handlers that redirect-after-POST so that executing a RELOAD/REFRESH on the client side doesn't end up repeating the transaction (and potentially creating two new database records, etc.). I recently discovered that a redirect-af