#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
-------------------------------------+-------------------------------------
Comment (by Adam (Chainz) Johnson):
The check can use `settings.is_overridden` to check that the user has set
it, rather than it being the default coming from the global settings file
:)
I posted this ticket because it happened to me, found a project that had
both configured and it wasn't clear which was intended by the original
developer.
--
Ticket URL: <https://code.djangoproject.com/ticket/30714#comment:2>
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.a8ad9b7611b466d60db6a2bd2e9923c8%40djangoproject.com.
