#30304: Support setting Secure, HttpOnly, SameSite on the language cookie
-------------------------------------+-------------------------------------
Reporter: Ran | Owner: nobody
Benita |
Type: New | Status: new
feature |
Component: | Version:
Internationalization |
Severity: Normal | Keywords: language cookie
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I propose to add the following settings, with the following default
values:
{{{
LANGUAGE_COOKIE_SECURE = False
LANGUAGE_COOKIE_HTTPONLY = False
LANGUAGE_COOKIE_SAMESITE = None
}}}
The default values maintain the current behavior.
These settings do not provide much security value, since the language is
not secret or sensitive. This was also discussed briefly here:
https://github.com/django/django/pull/8380#discussion_r112448195. The
reasons I'd like to add them are:
1. Sometimes auditors require them.
2. I personally prefer to set them unless I have a reason *not* to.
3. Browsers are starting to strongly nudge toward HttpOnly and Secure when
possible, e.g. https://webkit.org/blog/8613/intelligent-tracking-
prevention-2-1/.
--
Ticket URL: <https://code.djangoproject.com/ticket/30304>
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/051.6bd610b9842b4b1e45be33c9662a7a62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
