z_url_fetch: fix a problem where Spotify returns gzip content encoding when asked for identity #86
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.
If a Spotify url like
https://open.spotify.com/episode/6h3Z16AX2i1zy64L9K3yrx?si=584f101d1e734bf1
is fetched withaccept-encoding: identity
then Spotify returns gzip encoded content data.This fixes that problem by checking the content-encoding header, and in case of
gzip
try to decode the content using zlib.