#16046: Document best practices around using request.is_secure() in reverse
proxy
environments
----------------------------------+-------------------------------
Reporter: adamnelson | Owner: nobody
Type: Cleanup/optimization | Status: new
Milestone: | Component: Documentation
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
----------------------------------+-------------------------------
As evidenced in these locations:
* #14597
* https://github.com/rossdakin/django-heroism
* http://packages.python.org/django-middleware-extras/usage.html
* http://yuji.wordpress.com/2008/08/15/django-nginx-making-ssl-work-on-
django-behind-a-reverse-proxy/
* #6548
There is a need to document a best-practices way of handling an upstream
django server (Gunicorn, etc...) behind a reverse proxy (Nginx, etc...)
using the request.is_secure() method.
--
Ticket URL: <http://code.djangoproject.com/ticket/16046>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
