nginx as reverse caching proxy for CentOS repositories
mdounin at mdounin.ru
Thu Mar 18 23:51:19 MSK 2010
On Thu, Mar 18, 2010 at 07:30:02PM +0100, Wouter Schoot wrote:
> Could this somehow be related to http 1.1 to the client and 1.0 to
> the backend? Will that mess up the Range header? Any idea's ?
Have you actually tried looking into your client's code as
I've already suggested?
Given the fact that there are multiple requests with Range header
and some of them replied with 200 (and full content) it's pretty
obvious that client which doesn't handle 200 correctly will get
garbled result. And you can't do anything with it without
actually fixing client (or stopping it somehow from using range
More information about the nginx