Repository navigation
fix(network): cancel the auth challenge in AuthRequest#abort instead of failing the request - #700
Merged
Merged
Conversation
…of failing the request Chrome rejects Fetch.failRequest for a request paused on an auth challenge, so abort raised BrowserError and the page hung. Respond with CancelAuth through Fetch.continueWithAuth instead.
This file contains hidden or 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.
AuthRequest#abortsentFetch.failRequest, which Chrome rejects for a request paused on an auth challenge (BrowserError: authChallengeResponse required.). The error was swallowed in the event callback and the page hung. The fallbackrequest.abortat the end ofNetwork#authorizehit it too.It now responds with
CancelAuththroughFetch.continueWithAuth, so the page loads the unauthorized response.