Hi Sprow, > > < HTTP/1.1 200 OK > > < Date: Thu, 18 Jun 2015 10:37:44 GMT > > < Server: Apache > > < Last-Modified: Wed, 22 Oct 2014 18:23:45 GMT > > < ETag: "69c012-5cb89-506070c552e40" > > < Accept-Ranges: bytes > > < Content-Length: 379785 > > == < Content-Type: application/x-gzip > > == < Content-Encoding: x-gzip > > > > Perhaps they've fixed it, but it's compressed here. > > > > 379,785 bytes arrive, decompressing into 1,699,840. Could your HTTP > > client be decompressing it without you asking? > > Curious! > > Chrome delivers 1.6MB and what is plainly a tar file. Internet > Explorer delivers 370KB as you describe. > > So it is indeed a browser/webserver setup funny by the looks of it,
I thought this sounded familiar, and it is a long-standing marutan.net bug. http://www.riscos.info/pipermail/rpcemu/2010-May/000986.html The .tar.gz is being served as application/x-gzip above. To then say its Content-Encoding is x-gzip states it has been compressed again. Relatedly, Chrome 43 stops trying to cope with this kind of thing. Cheers, Ralph. _______________________________________________ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
