Content-Range header problem

[Nathan Kinkade]

Hi all,

For some reason Varnish (2.0.4) doesn't seem to be respecting the
Content-Range header, so our users are unable to resume large
downloads that somehow got interrupted.  Is this expected and normal
behavior, or should this work?  Do we need to add a rule in vcl_recv
that passes any incoming requests containing a Content-Range header
directly to the backend?

Thanks,

Nathan