Redirect loop behind a TLS-terminating proxy when SECURE_PROXY_SSL_HEADER is unset
A Django deployment served behind a reverse proxy that terminates TLS is documented to look like plain HTTP to the application unless SECURE_PROXY_SSL_HEADER is configured. When SECURE_SSL_REDIRECT is enabled at the same time, Django keeps redirecting an already-HTTPS request back to HTTPS, producing a redirect loop. Locally, without a proxy, the same settin