Add xhrChallengeType option #39
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Browsers such as Safari intercept 401 Unauthorized responses with the Basic challenge. In client side apps using XHR requests this creates a browser authorization dialog before you can handle the error in your own code.
The way around this is to change the challenge type on XHR requests. See the below links for more info:
http://stackoverflow.com/questions/86105/how-can-i-supress-the-browsers-authentication-dialog/20221330#20221330
http://loudvchar.blogspot.ca/2010/11/avoiding-browser-popup-for-401.html
I've added the
xhrChallengeTypeoption which works around this. Also added a test and updated the readme.