#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* cc: Carl Meyer (added)
* easy: 1 => 0
Comment:
Carl, any input about the intended use case of `SECURE_SSL_HOST`? I didn't
find any details in the [https://github.com/carljm/django-
secure/commit/51d0ce06928eff99a92a630ff0255e59ba77c86d django-secure
commit].
--
Ticket URL: <https://code.djangoproject.com/ticket/28359#comment:8>
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.7ba5b4945e52ea0bec73761acdfc614d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
