Just curious about redirect defaulting to 301.  Wouldn't 302 be more
appropriate?  Almost every time I need a redirect it's after a POST.
Asp and asp.net use 302 as does Ruby on Rails.  301 indicates a
permanent move and I'm wondering how often you need to do a permanent
redirect in code versus a 302 redirect after a POST.

I've seen some confusion in the forum because of the use of See Other
(303).  The documentation for See Other code 303 (http://www.w3.org/
Protocols/rfc2616/rfc2616-sec10.html) seems to indicate that 303 is
the right choice but Firefox does not handle a 303 according to the W3
documenation.  Try it, you'll get the warning prompt about re-posting
data.

Here is an interesting ticket for Rails where they try to make it "do
the right thing" http://dev.rubyonrails.org/ticket/1923.  Notice that
is appears to be closed with the 302 behaviour.

So I guess I'm suggesting redirect default to 302 to conform to
convention.  I think new users would be saved a lot of pain by this
change.  I know it would have saved me some grief.

Regards
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to