-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out why redirects aren't working #937
Comments
It appears that locally it's doing a 301. That's...not ideal, as the redirect I want to use for now will eventually be disabled to hit pages served by Mezzanine From https://docs.djangoproject.com/en/2.0/ref/contrib/redirects/ |
Here's what I found out:
In order to fix this, our handler404 can't set the response code to 302 before the redirect middleware executes. I see two ways forward:
|
Then yeah, let's stick with option 1. What's the actual work required for that? It might be something we can leave up for a contributor to pick up if they're interested until someone on the team has a chance to get to it. |
Will this be resolved once Wagtail is handling our 404's? |
It should be resolved once we stop relying on a statically built frontend that's served via whitenoise. |
Will redirects work now? |
Not yet, we still need fix the problems outlined in this comment |
We have stopped serving those pages statically, and I believe I added a djano-based 404 page last week. |
if it's ready to go, we should update this line so that it's not a redirect to a static page. |
Redirects added at https://foundation.mozilla.org/admin/redirects/redirect/ aren't working (they 404). Let's figure out why.
The text was updated successfully, but these errors were encountered: