fix: actually compress body with gzip when enableCompression is true#152
Merged
fix: actually compress body with gzip when enableCompression is true#152
Conversation
Previously, transformRequest set Content-Encoding: gzip header but
returned plain JSON.stringify(data), causing 500 errors on child
entity endpoints (e.g. POST /Quotes/{id}/Items, POST /Tickets/{id}/Notes)
that strictly validate the encoding header.
Now uses zlib.gzipSync to compress the body when enableCompression is
true, matching the declared Content-Encoding.
Fixes #151
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.
Fixes #151.
transformRequestsetContent-Encoding: gzipbut returned plainJSON.stringify(data), causing 500 errors on child entity endpoints that strictly validate the encoding header.Fix: Use
zlib.gzipSyncto compress the body whenenableCompression: true, matching the declared header.