#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
-------------------------------------+-------------------------------------
Comment (by Yoshiki Shibukawa):
OK, I understand.
I notified my fix is wrong. In some cases programmers assume method change
(e.g. POST then move to result page).
I think adding two new redirect classes is better way to support 307/308.
thank you. I will discuss.
--
Ticket URL: <https://code.djangoproject.com/ticket/30582#comment:3>
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.97b5d023bb190c1d80e35fd478d62d22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
