#32571: CsrfViewMiddleware assumes referer header can be parsed -------------------------------------+------------------------------------- Reporter: Chris Jerdonek | Owner: nobody Type: Bug | Status: new Component: CSRF | Version: 3.1 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted referer,CSRF,CsrfViewMiddleware | Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak): Replying to [comment:2 AdamDonna]: > Should the response in this scenario be something like this line? Or would a different response reason make more sense https://github.com/django/django/blob/45814af6197cfd8f4dc72ee43b90ecde305a1d5a/django/middleware/csrf.py#L248 Yes, we should reject immediately. -- Ticket URL: <https://code.djangoproject.com/ticket/32571#comment:3> 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/067.86933a64b81175d576405e519750d1a8%40djangoproject.com.