#30714: Add a system check against SESSION_EXPIRE_AT_BROWSER_CLOSE and
SESSION_COOKIE_AGE both being set
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: New feature | Status: closed
Component: contrib.sessions | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
I'm not sure about this.
`SESSION_COOKIE_AGE` defaults to two weeks. (OK, one thinks). I don't
touch that. I simply enable `SESSION_EXPIRE_AT_BROWSER_CLOSE` and all of a
sudden I get a warning?
That seems less than ideal.
Either we need to rationalize these settings somehow. (Maybe
`SESSION_COOKIE_AGE == 0` entailing `SESSION_EXPIRE_AT_BROWSER_CLOSE`?) Or
accept that whilst related they're not strictly interdependent.
Happy to think about it, but a decision is needed first no? Going to say
`wontfix` plus possible discussion on DevelopersMailingList for that
reason. Happy to reopen later if we can come up with something.
--
Ticket URL: <https://code.djangoproject.com/ticket/30714#comment:1>
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/068.650c068baf0fb1fa9331324f344e211b%40djangoproject.com.
