Ok the RFC reads on Partial Content
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.7)...

- Either a Content-Range header field (section 14.16) indicating
        the range included with this response, or a multipart/byteranges
        Content-Type including Content-Range fields for each part. If a
        Content-Length header field is present in the response, its
        value MUST match the actual number of OCTETs transmitted in the
        message-body.

What do they mean by the message-body? Is it the data about to be
recived or the header data?

Daniel Stenberg wrote:

> On Wed, 16 Mar 2005, Daniel Czarnecki wrote:
>
>> HTTP/1.1 206 Partial Content
>
> ...
>
>> Content-Length: 0
>
> ...
>
>> Content-Range: bytes 3715816-16703509/16703510
>
>
> I am pretty sure these two contradicting headers are the reason to the
> confusion. I don't have the RFC in front of me right now to check, but
> this looks very wrong in my eyes.
>
> Can you dig up the RFC to see what it says for a case like this?
>
Received on 2005-03-16