AsyncHttp: Support transfer-encoding #112
Closed
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
An exploration to support Transfer-Encoding: chunked and Content-encoding: gzip. A larger refactor may need to follow.
|
Superseded by #113 |
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.
An exploration to see what kind of internal refactor might be required to support
Transfer-Encoding: chunkedandContent-encoding: gzip. Related to #104. cc @maypaw – I took a stab on this one as I worry it might soon become a blocker for the data liberation work like downloading asset files, see WordPress/data-liberation#74.There's no test plan yet, other than running
php http_api.php.