New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
".tgz" files somtimes decompressed in error. #437
Comments
For further clarification and provide workarounds for anyone that lands here from google: The problem occurs when accessing $response->body. The below code will errantly decompress the .tgz file:
Easiest work-around I've found is to save the file using $options and avoid accessing $response->body:
If the intact body is needed for further processing, extract it from $response->raw:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requests.php will mistakenly decompress a .tgz file (or other gzipped files) downloaded from sites that pass a "content-encoding: none" header.
In the case of .tgz files, you end up with a misnamed, uncompressed tar file. Often manageable, but not if there needs to be an md5/sha1/etc checksum confirmation.
The decompress code is wrapped by
if (isset($return->headers['content-encoding']))
, so the decompress code fires even though the encoding is "none". Should there be a check for a proper encoding type, or at minimum, check for "none" before decompressing?Ran into this with bitbucket. A sample file to demonstrate the issue: https://bitbucket.org/jerrm-bb/testdownload/downloads/outcnam-test.tgz
The text was updated successfully, but these errors were encountered: