#35800: Clarify SECURE_PROXY_SSL_HEADER as it relates to the wsgi.url_scheme
environ
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: HTTP handling | Version: 5.1
Severity: Normal | Resolution:
| worksforme
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
I raised a related discussion the Forum a while back about whether we need
[https://forum.djangoproject.com/t/do-we-need-an-easier-toggle-for-
request-is-secure-to-be-true/20751 an easier control for the request's
is_secure()] method. It's not clear there's a consensus there as yet.
I think getting into WSGI details in the Django docs is not a good idea.
Wrapping the WSGI application is available, but it's not something we want
to point at too heavily IMO.
--
Ticket URL: <https://code.djangoproject.com/ticket/35800#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070192476a3dda-9b4c5970-d67f-40a5-b250-54b4fd90f3d8-000000%40eu-central-1.amazonses.com.
