[Seaside-dev] HTTP 302 vs 303

[Johan Brichau]

They changed the spec [1] to reflect the state of the practice.

I did not read it through yet, but it seems we can forget about this issue.

[1] http://evertpot.com/http-11-updated/

Sent from my iPad

> On 17 Feb 2014, at 18:04, Tobias Pape <Das.Linux at gmx.de> wrote:
> 
>> On 17.02.2014, at 17:26, Philippe Marschall <philippe.marschall at gmail.com> wrote:
>> 
>> Hi
>> 
>> I came upon this HN thread [1]. The linked article suggests we should
>> use HTTP 303 instead of 302 (because we want a change from POST to
>> GET).
>> 
>> [1] http://insanecoding.blogspot.ch/2014/02/http-308-incompetence-expected.html
> 
> But we have to make sure, the line is speaking HTTP1.1, right?
> (see note in http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.4)
> 
> Best
>    -Tobias
> 
> 
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20140607/54266d3b/attachment.htm