#20825: Make cookies use the HTTPOnly flag by default
-------------------------------+------------------------------------
Reporter: julien | Owner: julien
Type: New feature | Status: closed
Component: HTTP handling | Version: 1.5
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by erikr):
* status: new => closed
* resolution: => wontfix
Comment:
I completely concur. For the `set_cookie` default, I do see a security
benefit, but I feel it's so small that it's not worth breaking the
backwards compatibility. Especially when considering that this is likely
to break things silently, and not be noticed in unit tests - only by vague
error reports from users.
--
Ticket URL: <https://code.djangoproject.com/ticket/20825#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/064.e01ef18c31dbe4b702ff24184c8d8712%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
