#32005: Allow disabling of auto-404-redirection in LocaleMiddleware
-------------------------------------+-------------------------------------
Reporter: Alex Vandiver | Owner: nobody
Type: New feature | Status: new
Component: | Version: 3.1
Internationalization |
Severity: Normal | Resolution:
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 Alex Vandiver):
Replying to [comment:2 Carlton Gibson]:
> Looks like you've just introduced this issue here
https://github.com/zulip/zulip/commit/536bd3188e9428993fd712ed2f0df7c160b6ad60
🤔
That's the commit which introduces the need for it, and and works around
its lack; you can see it cites this ticket in so doing.
As noted in that commit message, the LocaleMiddleware needs to be
''before'' the middleware that throws the 404, in order for the 404 page
to be able to be properly localized. That's what now causes the
LocaleMiddleware to intercept the 404 and turn it into a 302.
--
Ticket URL: <https://code.djangoproject.com/ticket/32005#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/064.27f329f298342dbda568e3f72e24b6b1%40djangoproject.com.
