Skip to content

AsyncHttp: Support transfer-encoding - #112

Closed
adamziel wants to merge 2 commits into
trunkfrom
support-transfer-encoding
Closed

adamziel wants to merge 2 commits into
trunkfrom
support-transfer-encoding

Conversation

@adamziel

@adamziel adamziel commented Jul 13, 2024 •

Copy link
Copy Markdown
Collaborator

An exploration to see what kind of internal refactor might be required to support Transfer-Encoding: chunked and Content-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.

An exploration to support Transfer-Encoding: chunked and
Content-encoding: gzip. A larger refactor may need to follow.
@adamziel adamziel added HTTP Client enhancement New feature or request labels Jul 13, 2024
@adamziel

Copy link
Copy Markdown
Collaborator Author

Superseded by #113

@adamziel adamziel closed this Jul 15, 2024
@sirreal
sirreal deleted the support-transfer-encoding branch April 8, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request HTTP Client

Projects

No open projects
Archived in project

Development

Successfully merging this pull request may close these issues.

1 participant