fix: emit network.responseCompleted
for redirects
#2098
Merged
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.
Currently we never await the
responseReceivedExtraInfo
as we destroy the BiDiNetworkRequest
as soon as we see the redirect happening. This means that the conditions for emitting are never met.We should eventually change this but having the
responseCompleted
event with missing headers is better then not having it at all.Such change would mean that can never have order that matches the expectations
beforeRequestSent
->responseCompleted
->beforeRequestSent
As the
responseReceivedExtraInfo
comes after the second CDPrequestWillBeSent
#2035