Am 04.10.2005 um 22:00 schrieb Stephen Deasey:
The tests contain examples of valid and invalid range headers.
There's a also reference to the RFC.
See: tests/http_byteranges.test.
I think they're actually pretty complete, so if the tests pass you
haven't broken anything :-).But if you see
On 10/4/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 04.10.2005 um 09:37 schrieb Zoran Vasiljevic:
>
> > Hi,
> >
> > Vlad, you have made the ParseRange() call in the fastpath.c.
> > Can you help me understand the "Range:" header layout?
> > Is it something like:
> >
> >Range: bytes=a-
Am 04.10.2005 um 09:37 schrieb Zoran Vasiljevic:
Hi,
Vlad, you have made the ParseRange() call in the fastpath.c.
Can you help me understand the "Range:" header layout?
Is it something like:
Range: bytes=a-b,c-d,e-f
or
Range: bytes=-a
Or, can it only be:
Range: bytes=a-b
or
Hi,
Vlad, you have made the ParseRange() call in the fastpath.c.
Can you help me understand the "Range:" header layout?
Is it something like:
Range: bytes=a-b,c-d,e-f
or
Range: bytes=-a
Or, can it only be:
Range: bytes=a-b
or
Range: bytes=-a
I have some trouble understanding
