add gzip compression/decompression support#332
Merged
Conversation
61ff999 to
bc7e46d
Compare
Coverage Report for CI Build 177Coverage increased (+1.9%) to 78.405%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
bc7e46d to
6c142d8
Compare
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.
This PR introduces
gzipcompression/decompression support formoonbitlang/async:moonbitlang/async/internal/gzip_internalprovides state-machine style, IO-independent gzip encoding/decoding supportmoonbitlang/async/gzipprovides streaming gzip encoding/decoding support in the form of@io.Reader/@io.Writertransformer@http.Clientcan now automatically utilize HTTP gzip compression. It works as follows:Accept-Encoding, automatic decompression will be skipped, the user get raw, encoded traffic when reading the response, and must manually decode the trafficAccept-Encoding,@http.Clientwill setAccept-Encoding: gzip,identityas a default. In this case, if theContent-Encodingisgzipfrom the server response, the client will perform automatic decompression, so the user still get uncompressed result, as intendedContent-Lengthfield will no longer be visible to the user (even if it is present) to avoid confusion, because it stores length of compressed content