Weblate behind BunkerWeb reverse proxy

[tomkolp]

Running Weblate behind a reverse proxy (BunkerWeb). UI shows X-Forwarded-Proto: https but the diagnostic “Configured value” for protocol is still http. Is this expected or a bug, and what minimal proxy/env setup guarantees Django.request.is_secure() == True?

Anonymized data (exactly as observed, redacted):

HTTP environment (anonymized)
Observed / Configured
Client IP: x.x.x.x
Host HTTP: example.weblate.domain    example.weblate.domain
Protocol HTTP: https    http

Observed request headers (anonymized)
Cookie: [redacted]
Host: example.weblate.domain
Connection: close
X-Forwarded-For: x.x.x.x
X-Real-Ip: x.x.x.x
X-Forwarded-Proto: https
X-Forwarded-Protocol: https
X-Forwarded-Host: example.weblate.domain
X-Forwarded-Prefix: /
...

Environment docker conf:

WEBLATE_ENABLE_HTTPS: "1"
WEBLATE_SECURE_PROXY_SSL_HEADER: "HTTP_X_FORWARDED_PROTO,https"
USE_X_FORWARDED_HOST: "True"
WEBLATE_SECURE_SSL_REDIRECT: "True"
SESSION_COOKIE_SECURE: "True"
WEBLATE_IP_PROXY_HEADER: "HTTP_X_FORWARDED_FOR"
WEBLATE_USE_X_FORWARDED_PORT: "true"

@nijel

[nijel]

It's shown wrongly, create #16841 to track this.