<div class="gmail_quote">On Mon, Apr 5, 2010 at 2:46 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<div><div></div><div class="h5"><br>
On Sun, Apr 04, 2010 at 11:23:32PM +0530, Vinay Y S wrote:<br>
<br>
> Hi,<br>
> I've configured nginx to run as a http reverse proxy with caching turned on<br>
> for a location. The backend server supports range headers and responds<br>
> correctly with 206 partial content response. This is needed to support<br>
> pause/resume functionality in the browsers and download managers and also to<br>
> support download accelerator clients.<br>
><br>
> But with nginx reverse proxy with caching enabled, it seems to not work.<br>
> nginx returns full response even when range header is present. Is this a<br>
> known issue?<br>
> Please help fix this.<br>
<br>
</div></div>nginx removes Range header (as well as several other headers)<br>
before passing request to upstream to make sure full response will<br>
be cached and other requests for the same uri will be served<br>
correctly.<br><br></blockquote><div> It's fine for it send full request to the upstream so that it can cache the full response. Actually range requests and 206 responses work correctly when caching is not enabled. So, even when caching is enabled, it can still respond correctly to the client by obeying the range header, isn't it? Is this not implemented consciously for some reason?</div>
<div><br></div><div>Thanks,</div><div>-- </div><div>Vinay</div></div>