#23531: APPEND_SLASHES behavior shouldn't redirect with a 301
-------------------------------------+-------------------------------------
Reporter: mattrobenolt | Owner: nobody
Type: Bug | Status: new
Component: Core (URLs) | Version: master
Severity: Normal | Resolution:
Keywords: common, middleware, | Triage Stage:
redirect | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
I am not convinced about changing the default redirect as I expect the
majority of users with `APPEND_SLASHES` and `PREPEND_WWW` would want the
SEO benefits of a 301 redirect and are not going to change their URLs
after their site is deployed. This likely needs a wider discussion on
django-developers.
In the meantime, I think we can move forward with adding
`CommonMiddleware.response_redirect_class` as a separate ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/23531#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.e1bdfa5cb25d49a750ffa02d03b252b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
