CsrfViewMiddleware is too strict on referer checking for secure requests
|Reported by:||Paul McLanahan||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
In a project we'd like to have forms exist on an insecure page, but submit to a secure URL, and be CSRF protected using the middleware. This is currently impossible due to the middleware checking for "https" in the referer header for secure requests. I feel this is too strict and a check for the same host would be sufficient if any referer check is required at all. The comment in the code above these lines even suggests that the check may be too strict.
The lines to which I'm referring are 134 - 137 in
I'll be happy to provide a patch if a course of action is decided upon in the discussion.