Content-Range header problem

Kristian Lyngstol kristian at
Wed Sep 16 19:29:58 CEST 2009


On Wed, Sep 16, 2009 at 01:16:20PM -0400, Nathan Kinkade wrote:
> 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?

We currently do not have support for range-headers, so you'll have to pipe
these requests. Note that pass wont do the trick, since it'll still be
"cached"/buffered in varnish (but immediately discarded).

Kristian Lyngstøl
Redpill Linpro AS
Tlf: +47 21544179
Mob: +47 99014497
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <>

More information about the varnish-misc mailing list