[Nitro] Render#redirect question
lasso at lassoweb.nu
Fri Jun 9 02:45:01 EDT 2006
Seems I skipped some important bits when reading the specs. You're
completely right Bryan, there area some problems when using the 302
header. I found a very interesting article concerning this issue:
Maybe nothing should be changed until all implications are sorted out.
> On 6/8/06, Lars Olsson <lasso at lassoweb.nu> wrote:
>> According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html the
>> difference between a 302 and a 303 status codes is that the 303 status
>> code explicitly tells the browser to use a GET request when redirecting.
>> The 302 allows POST and HEAD as well. The 'patch' is as simple as
>> changing the default for the status parameter to 302 instead of 303.
> I'm not so sure that's the only difference... Nice link by the way. :)
> 10.3.3 302 Found
> The requested resource resides temporarily under a different URI.
> 10.3.4 303 See Other
> The response to the request can be found under a different URI and
> SHOULD be retrieved using a GET method on that resource.
> The response code of 303 seems more in line with typical usage, i.e.
> redirecting to a login screen for protected content, but that's just
> my opinion and a relatively uninformed one at that, in regards to HTTP
> response codes.
> Should it be 302 rather than 303? Opinions anyone? :)
> Nitro-general mailing list
> Nitro-general at rubyforge.org
More information about the Nitro-general