Re: User confirmation and 307 redirects

On 19.08.2010 13:58, Anne van Kesteren wrote:
> On Thu, 19 Aug 2010 12:16:58 +0200, Julian Reschke
> <julian.reschke@gmx.de> wrote:
>> On 19.08.2010 11:54, Yves Lafon wrote:
>>> ...
>>> Only for non-safe operations, and it was already the case for 301 in
>>> 2616. Also "harmful to interoperability" is an untestable claim.
>>> ...
>>
>> Which reminds me that the much more serious interop problems for 307
>> redirects on POST is that Safari is rewriting the message to GET. I
>> know this problem has been reported to Apple over two years ago...
>
> 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.

Best regards, Julian