Opened 3 weeks ago
Last modified 3 weeks ago
#35450 new Cleanup/optimization
Missing documentation: deploying Django in production behind a proxy.
Reported by: | Klaas van Schelven | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 5.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When Django is deployed behind a proxy (with https), various settings _must_ be set for your site to work correctly. Currently, there is no single place where these settings are documented. That is, they are mentioned in the general docs for settings (with a warning "only do this when behind a proxy) but there is no page "how to set up Django behind a proxy", which means to do this you must now puzzle various Stack Overflow / blog posts together.
The variables that I could find are SECURE_PROXY_SSL_HEADER
, USE_X_FORWARDED_HOST
and USE_X_FORWARDED_PORT
(if the port is not included in the host), but there may be more.
Change History (1)
comment:1 by , 3 weeks ago
Component: | Uncategorized → Documentation |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Cleanup/optimization |
There's need talk that the Django docs should better help with deployment, so I would happily review PRs on this.