New session backend instance does not respect a session_key parameter.
|Reported by:||niwi||Owned by:||nobody|
|Cc:||niwi@…||Triage Stage:||Design decision needed|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When I create an instance of the backend session with a specified key, if this key does not exist, creates a new key without respecting the one I specifically forced.
Is appropriate behavior? In my point of view, No.
This complicates a lot to create sessions with specific keys and forces me to do ugly hacks. That's because I have to access the low level API specific backend to create them the key. (This generates backend dependent code)
I hope I have explained well.
Test cases to reproduce the bug: https://github.com/niwibe/django/compare/bug/session-key
Change History (2)
comment:1 Changed 4 years ago by niwi
- Cc niwi@… added
- Has patch set
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset