Feature Request #3034
Request::redirect() $code parameter to be 303 as default (instead of 302)
|Assignee:||Woody Gilk||% Done:|
The code of 302 after POST submit causes browser to show the warning dialog, and sends the POST request it again if user agrees, while 303 does not do such a thing. Personally, I think that re-POST isn't something we, as developers, would want from regular users to do when it is not required, and so using 303 would be safer, and as such, the 303 should become a default value.
#1 Updated by Korney Czukowski about 4 years ago
I'm not sure about making it default, esp. since you may specify the code when using
Otherwise, there's a note (even though could be considered obsolete now):
Note: Many pre-HTTP/1.1 user agents do not understand the 303
status. When interoperability with such clients is a concern, the
302 status code may be used instead, since most user agents react
to a 302 response as described here for 303.