id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
35800	Clarify SECURE_PROXY_SSL_HEADER as it relates to the wsgi.url_scheme environ	Klaas van Schelven		"Looking at the documentation of [https://docs.djangoproject.com/en/5.1/ref/settings/#secure-proxy-ssl-header SECURE_PROXY_SSL_HEADER] it seems this is an absolutely required setting to get `is_secure` working correctly when behind a proxy.

However, this is not the case: Django's own WSGI handler inspects the environment value [https://wsgi.readthedocs.io/en/latest/definitions.html#envvar-wsgi.url_scheme wsgi.url_scheme]. 

This value is ""occasionally"" set, e.g. when running in the [https://docs.gunicorn.org/en/stable/settings.html#secure-scheme-headers default Gunicorn setup] (and it happens to be set based on the exact same header as in the case of Django).

This is surprising (in the bad way)... 

Perhaps the best way forward is simply to note that, depending on your wsgi server, such handling may already be in place (and that it uses the environment variable I mentioned)?"	Cleanup/optimization	closed	HTTP handling	5.1	Normal	worksforme		Carlton Gibson	Unreviewed	0	0	0	0	0	0