Responses to ranged requests

Per Buer perbu at varnish-software.com
Tue Apr 22 12:31:28 CEST 2014


On Tue, Apr 22, 2014 at 11:49 AM, Per Buer <perbu at varnish-software.com>wrote:

> On Tue, Apr 22, 2014 at 11:21 AM, Poul-Henning Kamp <phk at phk.freebsd.dk>wrote:
>
>> In message <CAOXZevBTrbUf7HGD=S-pH7k5Kchm5akj5F+vQCcXXap=
>> mM+qnA at mail.gmail.com>
>> , Per Buer writes:
>>
>> >moseleymark <https://www.varnish-cache.org/users/moseleymark> in the
>> forum,
>> >commented that Varnish responds with a "200 OK" when responding to ranged
>> >requests. Looking at the tests, that seems to be desired behavior.
>>
>> Test-case c00034 tells me that Varnish correctly responds with 206 if
>> it does respect the range, and 200 otherwise ?
>>
>> Do you have a case where this is not the case ?
>>
>
> User error. Both the user reporting it and I had syntax errors on the
> ranged requests and Varnish correctly responded with the whole content and
> a 200 error.
>
> Move along. Nothing to see.
>

The source of my confusion is that Varnish will respond with a "200 OK" on
a ranged request and give the whole document on a cache miss, whereas it
will respond as expected with the range on a cache hit.



-- 
 <http://www.varnish-software.com/> *Per Buer*
CTO | Varnish Software
Phone: +47 958 39 117 | Skype: per.buer
We Make Websites Fly!

Winner of the Red Herring Top 100 Global Award 2013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20140422/80cc1461/attachment.html>


More information about the varnish-dev mailing list