Downloaded file.tar.gz has wrong Checksum
Reported by
bochos1...@googlemail.com,
Jun 3 2016
|
||
Issue description<b>Chrome Version : <from About Google Chrome/Chromium></b> URLs (if applicable) : <b>OS version : <from About This Mac></b> Behavior in Safari 3.x/4.x (if applicable): Behavior in Firefox 3.x (if applicable): Behavior in Chrome for Windows: What steps will reproduce the problem? (1) Remember checksum for Binary (tar.gz) b21b0087a19c5ae043c66d1b60a6e1070336d15d openfire_4_0_2.tar.gz at http://www.igniterealtime.org/projects/openfire/ (2) Download File (3) verify checksum with openssl sha1 saf_openfire_4_0_2.tar What is the expected result? The given Chaecksum What happens instead? A different Checksum because the file is unzipped (not untared) Firefox Checksum is correct Safari also unzips the file but does not untar the checksum is the same like chrome Both Safari and Chrome hane a unaceptable behaviour because i could'nt verify the checksum Regards
,
Jun 3 2016
The content encoding is wrong:
--> HTTP/1.1 200 OK
Content-Type: application/x-tar
Content-Length: 22568870
Connection: keep-alive
Date: Fri, 03 Jun 2016 16:53:25 GMT
Content-Encoding: gzip
Last-Modified: Mon, 21 Mar 2016 18:34:14 GMT
ETag: "2b7e4fcb7b0df7197ed566da5c32431b-2"
Accept-Ranges: bytes
Server: AmazonS3
X-Cache: Miss from cloudfront
Via: 1.1 cbb2d834e8b935360bd9fa70ffe98378.cloudfront.net (CloudFront)
[...]
The content encoding requires that the UA decompress the body, which Chrome does.
|
||
►
Sign in to add a comment |
||
Comment 1 by shrike@chromium.org
, Jun 3 2016Labels: Needs-Feedback