#24280: CSRF cookie error only happening with Chrome.
---------------------------------+--------------------------------------
Reporter: jkapple | Owner: nobody
Type: Bug | Status: new
Component: CSRF | Version: 1.6
Severity: Release blocker | Resolution:
Keywords: CSRF, chrome | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by subsume):
I'd love to be able to reproduce it, still just debugging over email with
users (lots of them).
The docs do say "Regardless, you’re guaranteed to have the cookie if the
token is present in the DOM, so you should use the cookie!" is this true?
If so, the error message "not set" seems errant.
--
Ticket URL: <https://code.djangoproject.com/ticket/24280#comment:6>
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/065.ebc50698180128adf576f638bb948115%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
