Use the raw stream to prevent decoding the response#1435
Conversation
Use the raw stream to prevent decoding the response
|
This seems to cause the exact opposite error on other servers. |
|
Can you give an example? On Feb 5, 2014, at 2:28 PM, Tom Prince notifications@github.com wrote:
|
|
|
Also: |
|
So, the reason this happens is your server is gzip encoding a zip file and we no longer decode that by default because some servers if you tell them to serve a .tar.gz file they serve an Strictly speaking we should be decoding |
|
I also put a setuptools tar.gz there, and it gets double compressed and so pip chokes on it as well. |
|
Probably the right answer is to revert this, and make pip able to tell if we have a plain tarfile or a tar.gz even though the filename will be .tar.gz. Historically we've just used the filename for this. |
|
Grr, that's not completely right either, because it was breaking checksums too. Probably we're going to have to pick which one to support. |
|
This is a (I think) somewhat vanilla apache server. |
|
I would err on the side of not supporting silly server written by people that don't understand what HTTP headers are supposed to mean. |
|
No your server is doing it correctly. Well gziping a already compressed file is pointless, but it's not wrong. We switched to doing it incorrectly to fix things for one group, and that broke things for another group. Although I may have a different/better answer. If we can get requests to stop sending the accept header for gzip compression then I think the .tar.gz case this originally was trying to fix will still work and your server should work fine because it won't be compressing on the fly. I need to see if we can do that with requests and if so if it actually does that. |
|
Yeah. I just turned gzip compression off in the directory we are actually using, for .zip files. |
|
Yeah, also getting double compressed tar.gz with --find-links |
No description provided.