Author martin.panter
Recipients Jim.Jewett, abacabadabacaba, antialize, eric.araujo, jcea, jcon, jerub, jjlee, martin.panter, nadeem.vawda, orsenthil, rhettinger, ruseel, serhiy.storchaka, thomaspinckney3, vstinner
Date 2014-09-02.01:26:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409621217.82.0.902144791809.issue1508475@psf.upfronthosting.co.za>
In-reply-to
Content
I think the patch is indeed a bit short, for instannce it looks like calling read() without a size limit could bypass the decoding.

Also, I wonder if Content-Encoding handling is better done at a higher level. What if someone wants to download a *.tar.gz file? They may not expect the tar file to be transparently decompressed. And I suspect this would blow up if you tried a partial range request.

Transfer-Encoding is meant to be the proper way to transparently compress HTTP messages at a low level, but it doesn’t seem to be used as much in the real world.
History
Date User Action Args
2014-09-02 01:26:58martin.pantersetrecipients: + martin.panter, rhettinger, jjlee, jcea, orsenthil, jerub, vstinner, antialize, ruseel, nadeem.vawda, thomaspinckney3, eric.araujo, abacabadabacaba, jcon, Jim.Jewett, serhiy.storchaka
2014-09-02 01:26:57martin.pantersetmessageid: <1409621217.82.0.902144791809.issue1508475@psf.upfronthosting.co.za>
2014-09-02 01:26:57martin.panterlinkissue1508475 messages
2014-09-02 01:26:57martin.pantercreate