#32065: Documentation for settings.CSRF_COOKIE_DOMAIN confusing
-------------------------------------+-------------------------------------
Reporter: Anthony | Owner: Carlton
| Gibson
Type: Bug | Status: closed
Component: Documentation | Version: 3.1
Severity: Normal | Resolution: fixed
Keywords: cookie, domain, | Triage Stage: Ready for
csrf | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"f4db2d16ec42922078ff1951cd696c9b49e1e2f6" f4db2d1]:
{{{
#!CommitTicketReference repository=""
revision="f4db2d16ec42922078ff1951cd696c9b49e1e2f6"
[3.1.x] Refs #28741 -- Doc'd SESSION_COOKIE_DOMAIN requirement with
CSRF_USE_SESSIONS.
Similar considerations as refs #32065, again adding some nuance to
afd375fc343baa46e61036087bc43b3d096bb0ca.
Backport of 2e7ba6057cfc82a15a22b6021cd60cf307152e2d from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32065#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/066.47e24a590aa2a53c12bccbefc566d560%40djangoproject.com.
