#20825: Make cookies use the HTTPOnly flag by default
-------------------------------+------------------------------------
Reporter: julien | Owner: julien
Type: New feature | Status: new
Component: HTTP handling | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by raphaelm):
Actually, accessing the CSRF cookie via JavaScript is the recommended way
to use the CSRF protection with AJAX (see:
https://docs.djangoproject.com/en/1.8/ref/csrf/#ajax). So, as far as the
CSRF cookie is concerned, I'd close this as "wontfix".
As for set_cookie, this would break backwards compatibility and as the
most important cookie, the sessison cookie, is protected, I'd also vote
for wontfix here. Any other opinions?
--
Ticket URL: <https://code.djangoproject.com/ticket/20825#comment:2>
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.51e4ec055c05cb5a9e369f5ffaff479a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
