#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 mattrobenolt):
Ahh, ok, I like that.
Is it then suggested to subclass the middleware and override?
While on this topic... should the `APPEND_SLASHES` behavior be considered
to be stripped out into it's own middleware? Or is there value in having
it crammed inside `CommonMiddleware`?
I ask because if we introduce `CommonMiddleware.response_redirect_class`,
it feels ambiguous. Though there's only one redirect path in
`CommonMiddleware`, it just doesn't feel as concrete as
`LocaleMiddleware`.
--
Ticket URL: <https://code.djangoproject.com/ticket/23531#comment:7>
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/070.f059fce24901d0d828c14ea80456beb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
