Skip to content
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.

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

Doesn't work with WWW-Authenticate header #73

Open
panesofglass opened this issue Jul 8, 2014 · 2 comments
Open

Doesn't work with WWW-Authenticate header #73

panesofglass opened this issue Jul 8, 2014 · 2 comments

Comments

@panesofglass
Copy link

If I submit a WWW-Authenticate header back with the 401 response using Basic authentication, I still see the browser window pop-up. Any idea as to how I could block the browser's pop-up? I need to be able to authenticate users in the browser for other scenarios.

@Rykus0
Copy link

Rykus0 commented Aug 15, 2014

I believe the only way to avoid this is to change the response header from the server-side. So you could change it from WWW-Authenticate Basic ... to WWW-Authenticate xBasic ... or something.

@panesofglass
Copy link
Author

@Rykus0, that is what I found, as well. It is unfortunate, since I have other pages on the site I would like to protect in the same way that are not part of the Angular app. So I'm broken in one form or another. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants