#19778: csrf middleware report BAD_REFERER when HTTP_HOST contains port
--------------------------------+------------------------------------
Reporter: jens.tinfors@… | Owner:
Type: Bug | Status: closed
Component: contrib.csrf | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Changes (by bouke):
* status: new => closed
* resolution: => wontfix
Comment:
From the submitter
([[https://github.com/django/django/pull/705#issuecomment-30667890|comment
on GitHub]])
> Well, It's been almost a year since I submitted this pull request.
> I say in the comment above that you should probably disregard it.
> A year old bug!? If a bug at all!? "The tests fail in master", I shall
hope so, it's a year old.
> Let's close this one and move on shall we!
--
Ticket URL: <https://code.djangoproject.com/ticket/19778#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 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/080.c7fafc3f2036f2c48adb1fa4e340849c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
