That's the only upstream I'm aware of that works with proxies.

On 09/05/2014 23:05, Jonathan Matthews wrote:
> On 9 May 2014 13:36, Tom McLoughlin <me@tommehm.com> wrote:
>> I keep getting this error every time someone loads a page. subs
>> filter header ignored, this may be a compressed response. while
>> reading response header from upstream, client: xx.xx.xx.xx,
>> server: , request: "GET /search/sharepoint/0/7/0 HTTP/1.1",
>> upstream: "http://194.71.107.80:80/search/sharepoint/0/7/0",
>> host: "tpb.rtbt.me", referrer:
>> "http://tpb.rtbt.me/search/sharepoint/0/99/"
>
> So why not stop the upstream responding with a compressed
> response?
>
> I know how to do this for TPB, having written a *14* line nginx
> config to do exactly the same thing, reverse proxying TPB for ..
> academic reasons. But you're trying to make money off them, so I
> don't feel like sharing. I'll let you figure it out. It's really
> not difficult.
>
> J
>
> _______________________________________________ nginx mailing list
> nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx