Closed vcarciu closed 7 years ago
~Hmm this seems odd because the patch for that should have landed~ No it's a different path see next comment.
Here's the sentry report for it: https://sentry.prod.mozaws.net/operations/addons-frontend-amo-stage/issues/385485/
Ah ok - this sounds like it might be FXA config related.
The patch I referred to above being landed was actually to force a 404 for user/[USER]
whereas this path is users/edit/
.
Whilst config can probably prevent us hitting this URL, it would be good to add a route to force a 404 for this case so that we do still fall-back to the non-mobile site without blowing up.
Fwiw: I've just tried the same thing on our prod instance and a 500 occurs there the same.
The workaround in https://github.com/mozilla/addons-frontend/issues/2034 didn't work. Here's what happens:
addons-frontend
starts by serving a 404
for /users/edit/
addons-server
serve /users/edit/
addons-server
sees /users/edit/
and redirects to /users/edit
addons-frontend
sees /users/edit
and adds a slash to the endThe server change landed on stage and I was just about to sign in with a brand new account 🍨
Verified as fixed
Please see postfix video :
Steps to reproduce: 1.On Android, go to AMO-Stage and try to register
Expected results: After pressing confirmation link from confirmation email received, user is successfully logged to AMO-Stage
Actual results: Server error page is displayed and user is not logged in
NOTES: Same like https://github.com/mozilla/addons/issues/10058 , but on Stage