We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Once the nginx configs from #10266 are rolled out to stage and prod it would be good to remove the forced 404 routes that should no longer be needed.
See https://github.com/mozilla/addons-frontend/blob/c8e567e7b6b7098368123d12fa698855c8e00d44/src/amo/routes.js#L32
The text was updated successfully, but these errors were encountered:
This will be a little confusing (for local development only) since we won't see 404s anymore. I think we can get back to 404s after #10363
Sorry, something went wrong.
kumar303
Successfully merging a pull request may close this issue.
Once the nginx configs from #10266 are rolled out to stage and prod it would be good to remove the forced 404 routes that should no longer be needed.
See https://github.com/mozilla/addons-frontend/blob/c8e567e7b6b7098368123d12fa698855c8e00d44/src/amo/routes.js#L32
The text was updated successfully, but these errors were encountered: