#35450: Missing documentation: deploying Django in production behind a proxy.
----------------------------------------------+------------------------
Reporter: Klaas van Schelven | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------------+------------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/35450>
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/0107018f7620f028-d94c0e78-21f0-4196-b34d-10eb7b57ca11-000000%40eu-central-1.amazonses.com.
