Closed Bug 655285 Opened 15 years ago Closed 14 years ago

Reset password in the Account sign flow shows https://stage-account.services.mozilla.com/forgot/

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: petef)

References

Details

(Keywords: regression)

telliot points out the trailing / shouldn't be there. STR's 1) Add a new client to an account using "I don't have the device with me" link 2) direct custom server to stage. 3) Enter account name, an incorrect password and whatever in the sync key field. 4) Click Continue 5) Then click the Reset Password link Tested results: https://stage-account.services.mozilla.com/forgot/ with 404 is loaded expected results: https://stage-account.services.mozilla.com/forgot (no trailing slash) is loaded.
given the prevalence, we should probably add a redirect on account.services as well as fixing it.
Where is the URL generated? If I point the same client to production, the correct url is generated without the trailing slash.
The string 'forgot' does not appear in any relevant places in services-central. That is: the client doesn't know anything about the account portal, which I think answers your question, Tracy.
my suspicion is that there's a redirect from the services.mozilla page (and stage equivalent) and that's the actual problem here.
Confirmed - the problem is solely that stage-auth.services.mozilla.com/weave-password-reset is redirecting to forgot/. Someone just needs to go into nginx and kill that config. Handing over to ops. No production impact.
Component: Server: Registration → Operations
QA Contact: reg-server → operations
Assignee: nobody → petef
fixed in r14488 restarted nginx on stage with new config. % curl -q -v 'https://stage-auth.services.mozilla.com/weave-password-reset' 2>&1 | grep -w Location < Location: https://stage-account.services.mozilla.com/forgot
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
verified fixed in staging.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.