I don't think it's worth the deprecation path to rename the old classes - it doesn't seem like there's a substantial benefit to using the different codes and getting everyone to change their imports is a lot of work to impose on the world.
There must be some name for the 308 one that would work, but I can't think of one off the top of my head. The new class could also be mentioned in the 301/302 classes' docstrings. On Sun, 23 Sep 2018 at 06:56, Matthieu Bonnefoy <matthieu.bonne...@gmail.com> wrote: > Hi Adam, > > Thanks for your reply. > > I agree, I think that would be a nice addition. The issue we’ll have is > that the current naming of the HttpResponsePermanentRedirect (301 Moved > Permanently) will be confusing. > > existing > - HttpResponsePermanentRedirect (301 Moved Permanently) => should probably > be HttpResponseMovedPermanently > - HttpResponseRedirect (302 Found) => should probably be HttpResponseFound > > new additions > - HttpResponseTemporaryRedirect (307 Temporary Redirect) => probably ok > with the existing naming for 302 > - ? (308 Permanent Redirect) ==> naming conflict with the existing 301, > HttpResponsePermanentRedirect308? HttpResponsePermanentRedirection? > HttpResponsePermanentlyRedirected? … not super convinced by these > suggestions. What do you think? > > I could add the new responses and mention them in the documentation here > with the recommendation > > https://docs.djangoproject.com/en/2.1/ref/request-response/#httpresponse-subclasses > > We could also mention the 308 redirect at the end of the class docstring > here > https://docs.djangoproject.com/en/2.1/_modules/django/middleware/common/ > > Cheers, > Matthieu > > > > On Tuesday, 18 September 2018 23:55:17 UTC+12, Adam Johnson wrote: >> >> This is historical, 307 and 308 were added later, and I think we couldn't >> change it without breaking backwards compatibility. That said, 307 and 308 >> classes could be added to django.http.response and the documentation could >> recommend their use. Mozilla docs show that they're compatible with all >> tracked web browsers so most Django sites could use them. >> >> On Tue, 18 Sep 2018 at 07:14, Matthieu Bonnefoy <matthieu...@gmail.com> >> wrote: >> >>> Hi there, >>> >>> I am wondering why the default redirect class in the common middleware >>> is a 301 Moved Permanently response. >>> >>> https://github.com/django/django/blob/master/django/middleware/common.py#L32 >>> https://github.com/django/django/blob/master/django/http/response.py#L476 >>> >>> I just got the issue of a POST request being changed as a GET request by >>> the redirect and found it quite confusing. >>> It seems that a 308 Permanent Redirect (by the way the name of the >>> redirect subclass is now a bit confusing) is now widely supported and would >>> be a better option. >>> https://tools.ietf.org/html/rfc7538 >>> https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/308 >>> >>> +-------------------------------------------+-----------+-----------+ >>> | | Permanent | Temporary | >>> +-------------------------------------------+-----------+-----------+ >>> | Allows changing the request method from | 301 | 302 | >>> | POST to GET | | | >>> | Does not allow changing the request | 308 | 307 | >>> | method from POST to GET | | | >>> +-------------------------------------------+-----------+-----------+ >>> >>> >>> What do you think? >>> >>> Thanks, >>> Matthieu >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/django-developers. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/a9f807b8-d31c-4729-a9bc-ac80274d4590%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/a9f807b8-d31c-4729-a9bc-ac80274d4590%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> Adam >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/e9400ed9-f79b-4202-9f15-fa2addb3cf92%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/e9400ed9-f79b-4202-9f15-fa2addb3cf92%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1b-pr56qTpeGV6ZPnqKFeid4FOod4m4kzBxoUB0E_NxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
