#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN
------------------------------+--------------------
Reporter: mattrobenolt | Owner: nobody
Type: New feature | Status: new
Component: CSRF | Version: master
Severity: Normal | Keywords: csrf
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------
Right now, if you try to share a CSRF token across a subdomain without
https, everything works great since the Referer header isn't validated.
But over https, we want to be a bit more strict and make sure that the
Referer is from another secure site, and also that the Referer matches
where we think it should be coming from. The canonical source for where we
think it should be from is `CSRF_COOKIE_DOMAIN`.
If we set our `CSRF_COOKIE_DOMAIN` to `.example.com`, that means our CSRF
validation should work for `www.example.com` and `foo.example.com`. Not
just strictly the domain the request is coming from.
--
Ticket URL: <https://code.djangoproject.com/ticket/24496>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/055.6f73bfb3cbf2f1a92f335ed8174a3b13%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
