fix: base64 encode gzipped data #590
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
`string(gzippedData)` does not guarantee a UTF-8 sanitized string, which may lead to corrupted data.
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.
string(gzippedData)does not guarantee a UTF-8 sanitized string, which may lead to corrupted data.Also, returned the non-nil error from
GetFromSessionto make debugging easier and changed the test file to also encode the test data into base64.I was getting
gzip: invalid headerin my app and upon inspection found the sequence239 191 189repeated many times across the gzipped data, including in the gzip header.