#29025: Security middleware for insecure (HTTP) connections
--------------------------------+------------------------------------------
Reporter: Vishwas Mittal | Owner: Vishwas Mittal
Type: New feature | Status: assigned
Component: HTTP handling | Version: 2.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------------
Comment (by Vishwas Mittal):
Replying to [comment:2 Aymeric Augustin]:
> Why should Django reinvent HTTPS instead of simply recommend to use it?
Sometimes many users (including me) uses their Django server on the
computer only (for local networks) this can pose some problem of security
and sometimes for some servers (say for non-commercial purposes) the
server can be HTTP.
Here I am not saying to use it every time, there can be a check if the
network is not HTTPS then we can use it's protection else just bypass it.
--
Ticket URL: <https://code.djangoproject.com/ticket/29025#comment:3>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.0fda11373243109788a6f382281bf25e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
