Closed Bug 560260 Opened 11 years ago Closed 9 years ago
Treat 400, 401, 404 responses differently for logins
Right now we have.. 400: server error (* hits the default: case) 401: login rejected 404: login rejected We could actually identify them differently and expose that to the user: 400: invalid username (probably typed in an @email address) 401: login rejected (wrong password) 404: username doesn't exist (valid username format, but no account here)
Future for now, may re-evaluate later.
Target Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 730989
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.