Recognize HTTP/2 streaming #193
Open
Conversation
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
RasmusN
force-pushed
the
bugfix/support-HTTP-2
branch
2 times, most recently
from
5e0f453 to
9fb9043
Compare
Contributor
Author
|
I included the pipeline fix just to make sure CI passes. Let me know if you the commit removed |
The extension could reviously only recognize HTTP/1 streaming. HTTP/2 (TLS) doesn't allow the Transfer Encoding = "chunked" response header. This commit makes the extension look for other signs of streaming.
RasmusN
force-pushed
the
bugfix/support-HTTP-2
branch
from
04a0d53 to
1dd54f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The extension could reviously only recognize HTTP/1 streaming. HTTP/2 (TLS) doesn't allow the Transfer Encoding = "chunked" response header. This commit makes the extension look for other signs of streaming.
Fixes #192