#36339: BrokenLinkEmailsMiddleware fires when Referer is invalid and URL
redirects
-------------------------------+--------------------------------------
Reporter: Xeekoo4u | Owner: (none)
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Jake Howard):
I also find this issue strange. If you can reliably reproduce the issue
Xeekoo4u, It'd be great if you can try and diagnose what's going on with
`BrokenLinkEmailsMiddleware` yourself to point us in the right direction.
As Natalia says, the forum might also be a good place to get help on this
before circling back to this issue with some more context. Alternatively,
if you can get the issue working in a minimal project, that'd be helpful
too.
The part which makes me think there's something else going on here (rather
than it being merely a bug with `BrokenLinkEmailsMiddleware`) is the `if
response.status_code == 404` on the first line of the middleware, which
ought to avoid any issue like this.
--
Ticket URL: <https://code.djangoproject.com/ticket/36339#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701965c9a0a64-562746fe-7992-4276-ad4d-7e9c32d1e3dd-000000%40eu-central-1.amazonses.com.
