#30582: Redirect by using 307/308 instead of 301/302.
-------------------------------------+-------------------------------------
Reporter: Yoshiki Shibukawa | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: wontfix
Keywords: redirect statuscode | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* has_patch: 1 => 0
* resolution: => wontfix
Comment:
Thanks for the proposition. As you described 307/308 do not allow changing
the request method from POST to GET, so this change is backward
incompatible am I'm not sure if this should be a default Django behavior.
Please start a discussion on the DevelopersMailingList, we can re-open
this ticket if we reach a consensus on a mailing list.
--
Ticket URL: <https://code.djangoproject.com/ticket/30582#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f5418a9dfc91a98fafd6e4c3efa3bf8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
