#16010: Support Origin header checking in the CSRF middleware
-----------------------------+--------------------------------------
Reporter: davidben | Owner: Tim Graham
Type: New feature | Status: assigned
Component: CSRF | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by Adam Johnson):
Ah yes - the scheme, and port (if non-default), are part of the Origin.
Discarding them is not appropriate due to the security concern of leaking
HTTPS data to an HTTP origin. I moved django-cors-headers to require
schemes [https://github.com/adamchainz/django-cors-
headers/blob/master/HISTORY.rst#300-2019-05-10 in version 3.0.0].
--
Ticket URL: <https://code.djangoproject.com/ticket/16010#comment:11>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.667df0fec9b636a60b6721fa3659af20%40djangoproject.com.
