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.

Sign up for GitHub

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

Jump to bottom

401 handling from browser #4

Open

EfraimFeinstein opened this issue Jul 16, 2014 · 0 comments

Labels

bug

Member

EfraimFeinstein commented Jul 16, 2014

There is (at least) 1 circumstance where simply visiting the app can cause an immediate 403/401 password dialog from a browser.

Log in to browser#1 and remember credentials
Remove or disable the account or change the password in browser#2 without changing the auth information on browser#1 (do not log out).
Return to browser#1 (certainly using a direct URL like localhost:5555/texts/XXXX ) . You will get a persistent 401 dialog.

The correct behavior would be an error indicating that the username/password is invalid and a bounce back to the login page.

EfraimFeinstein added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment