#25125: Add a check in the checks framework for colliding LANGUAGE_COOKIE_NAME &
SESSION_COOKIE_NAME
----------------------------------+------------------------------------
Reporter: kezabelle | Owner: kswiat
Type: New feature | Status: assigned
Component: contrib.sessions | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
----------------------------------+------------------------------------
Changes (by kswiat):
* needs_better_patch: 0 => 1
Comment:
If I am not missing something, since there are no conventions/restrictions
about cookie naming and we do not track a list of cookie names, such a
generic check must wait till runtime (I mean, we don't know which setting
is a cookie name till then)?
Maybe we should replace colliding names enumeration in docs with something
like "cookie name must be unique"?
--
Ticket URL: <https://code.djangoproject.com/ticket/25125#comment:8>
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.91d9bd707e34d2c695b855fd6c386a3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
