#28359: SecurityMiddleware's SECURE_SSL_HOST only affects unsecure requests
-------------------------------------+-------------------------------------
Reporter: Matthias Kestenholz | Owner: (none)
Type: New feature | Status: new
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carl Meyer):
The intention of the setting was to provide some control over the
redirect-to-SSL functionality provided by SecurityMiddleware, and it does
that. I don't think SecurityMiddleware should be in the business of
enforcing a canonical host for all SSL requests. It's easy enough to write
your own middleware for that (and it can even use the value of
SECURE_SSL_HOST if you want). The current behavior is pretty clearly
documented; changing it would not be a bugfix but a change in the intended
behavior.
I agree that if we were implementing this from scratch, a reasonable case
could be made for the alternate behavior, but I don't think it's a strong
enough case for a backwards-incompatible change.
--
Ticket URL: <https://code.djangoproject.com/ticket/28359#comment:9>
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.4d84ba33015ee899d4909e6ade333f43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
