#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-------------------------------------+-------------------------------------
Reporter: Matthias Kestenholz | Owner: (none)
Type: New feature | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Matthias Kestenholz):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks, Tim and Carl.
I'm closing this ticket as wontfix. Maybe canonical URL redirection would
be a better fit for `CommonMiddleware` (since we have `PREPEND_WWW` there)
but it's easier and certainly less controversial to just implement this
outside Django core.
I'll add another Django package to my long list of maintained packages
then, and post the link here for posteriority :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/28359#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/067.6f4e8d89de7217eed546685ccab77e2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
