#33569: Add support for multiple values for the x-forwarded-proto header
-------------------------------------+-------------------------------------
Reporter: Thomas Schmidt | Owner: Thomas
Type: | Schmidt
Cleanup/optimization | Status: new
Component: HTTP handling | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hmmm. I think adding complexity here (at all) will come back and bite us.
> Which might be hard in cloud environments.
The issue is that there's no easy "I only use HTTPS switch", which is most
deployments these days. That makes folks rely on
`​SECURE_PROXY_SSL_HEADER`, which gets ever more tricky as deployments get
ever more baroque. Such a switch would solve most use-cases, I submit :)
Short of that, the lightest WSGI middleware setting `wsgi.url_scheme` in
the `environ` would be preferable to getting into parsing
`SECURE_PROXY_SSL_HEADER` (for me).
--
Ticket URL: <https://code.djangoproject.com/ticket/33569#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f730d9fec-ee3b5255-5771-4735-b7a7-36a2ad748cd4-000000%40eu-central-1.amazonses.com.
