Content-Range header problem
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 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Content-Range header problem
Hi, 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 pgpjLt5mA5sEr.pgp Description: PGP signature ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Content-Range header problem
On Wed, Sep 16, 2009 at 1:29 PM, Kristian Lyngstol krist...@redpill-linpro.com wrote: Hi, 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). Thanks. The resolution is simple, but I just wanted to be sure. In response to Michael's reply regarding why we are proxying such files, we haven't been doing it explicitly or on purpose ... it was just happening by default. We didn't have any explicit rules directories or files, though we may shortly after I finish this email. :-) Thanks again, Nathan ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Content-Range header problem
On Wed, Sep 16, 2009 at 01:36:00PM -0400, Nathan Kinkade wrote: Thanks. The resolution is simple, but I just wanted to be sure. Always nice to verify :) By the way, I just read the labs.cc.o post [1] from when you started using Varnish and I'm curious as to how you're doing now with regards to these issues? [1] http://labs.creativecommons.org/2008/04/03/varnish-cache-at-cc/ -- Kristian Lyngstøl Redpill Linpro AS Tlf: +47 21544179 Mob: +47 99014497 pgpvljKm80niY.pgp Description: PGP signature ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
