#23427: Doc update to account for runserver behavior when starting project
-------------------------------------+-------------------------------------
Reporter: patrickbeeson | Owner:
Type: | patrickbeeson
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.7
Severity: Normal | Resolution:
Keywords: docs tutorial | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by collinanderson):
If it helps, it's only an issue if you already have a `sessionid` cookie
for the domain, so it shouldn't be an issue for everyone.
As a side note, probably not possible with just middleware, but it would
be nice if the session authentication check was done the first time
`get_user(request)` is called, instead of every request, as it creates
unnecessary session and user queries on pages where user is not used. It
would be nice if there were a way to override the `get_user(request)`
logic to put this check there.
--
Ticket URL: <https://code.djangoproject.com/ticket/23427#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 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/071.18fc4fa5e164a252ac38f84baf42d1f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
