- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 19 Aug 2010 14:17:53 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: Yves Lafon <ylafon@w3.org>, Adam Barth <ietf@adambarth.com>, httpbis <ietf-http-wg@w3.org>, Maciej Stachowiak <mjs@apple.com>
On 19.08.2010 14:12, Anne van Kesteren wrote: > On Thu, 19 Aug 2010 14:09:20 +0200, Julian Reschke > <julian.reschke@gmx.de> wrote: >> On 19.08.2010 13:58, Anne van Kesteren wrote: >>> If you do not want to show UI or inform the user of something most users >>> cannot comprehend and you do not want to do something "dangerous" it >>> seems somewhat okayish to issue a GET instead. >> >> Yes, but in that case 307 is the wrong status code; use 303 instead. > > Except that the browser cannot control what status code the server > gives. o_O Well, the server knows what's supposed to happen. If the server wants you to do a POST to a new URI, and you don't want to do the POST, then doing a GET instead simply is a bug. Incorrect. Wrong. Bad. Best regards, Julian
Received on Thursday, 19 August 2010 12:18:34 UTC