reverse proxy + caching seems to break range requests

[Vinay Y S]

Hi,
I've configured nginx to run as a http reverse proxy with caching turned on
for a location. The backend server supports range headers and responds
correctly with 206 partial content response. This is needed to support
pause/resume functionality in the browsers and download managers and also to
support download accelerator clients.

But with nginx reverse proxy with caching enabled, it seems to not work.
nginx returns full response even when range header is present. Is this a
known issue?
Please help fix this.

Thanks,
Vinay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20100404/59a70f11/attachment.html>