On Wed, Apr 2, 2014 at 6:09 PM, ProgAndy <admin@xxxxxxxxxxx> wrote: > There may be a transparent proxy in your routing chain that strips > compression in order to run a virus scan. > The server sends these headers for haskell-core.db > ( curl -I http://xsounds.org/~haskell/core/x86_64/haskell-core.db ) > > Content-Type: application/x-tar > Content-Encoding: x-gzip > > It might work as expected without a Content-Encoding header: > > Content-Type: application/x-gzip Yes, you are probably right. I just didn't think anyone would actually configure a proxy to deliver the un-gzipped result to the client. That sounds like a way to break all kinds of things! I'll ask around here to see if this is the case. I don't have direct control over the server where the repo is, but I might be able to convince the admins that it's a bad idea to put Content-Encoding into reponses. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@xxxxxxxxxxxx jabber: magnus@xxxxxxxxxxxx twitter: magthe http://therning.org/magnus
