#21076: Offer the ability to store a hash of session IDs rather than the ID
itself
----------------------------------+------------------------------------
Reporter: Tim Graham | Owner: Mark
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: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Mark):
Requesting feedback about naming convention (see
[https://github.com/django/django/pull/8736#issuecomment-610986822 this PR
comment]) to make a clear distinction between incoming "clear text"
session keys and session keys that are stored in the sessions backend
(potentially hashed, but not necessarily, depending on settings and
existing session keys). My suggestion is to use the names `frontend_key`
and `backend_key` respectively.
Also requesting feedback concerning a refactor of the `SessionBase` API to
DRY-up the session key conversion (see
[https://github.com/django/django/pull/8736#issuecomment-611934012 this PR
comment]).
--
Ticket URL: <https://code.djangoproject.com/ticket/21076#comment:7>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.54c217d80a45a168e508e50666531eef%40djangoproject.com.
