#17103: Add HTTP Strict Transport Security support, to improve support for
all-SSL
sites
-----------------------------------------+------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: SVN
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 |
-----------------------------------------+------------------------
Since you pretty much shouldn't do anything with sessions or logins on a
public site without SSL, I think a solid majority of public Django sites
probably ought to be all-SSL. Given this, I think Django core should
provide good support for all-SSL sites out of the box.
[http://en.wikipedia.org/wiki/Strict_Transport_Security HSTS (HTTP Strict
Transport Security)] is an HTTP response header that allows a site to tell
a browser to only ever access it over HTTPS. This avoids the need for
redirect-to-SSL on repeat visits and reduces exposure to various types of
attacks.
There is an existing implementation of HSTS in
[http://pypi.python.org/pypi/django-secure django-secure].
--
Ticket URL: <https://code.djangoproject.com/ticket/17103>
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.
