shawn
shawn

Reputation: 4223

Is the HTTP content-range header compatible with chunked transfer encoding?

As above, is byte serving chunked transfer possible in the HTTP standard?

Upvotes: 6

Views: 2183

Answers (1)

npnmodp
npnmodp

Reputation: 1232

From RFC2616, Transfer-Encoding is a property of the message, not the entity. Content-Range is an entity-header. So in principle they can be used together, unless there exists some corner case where the two conflict.

Here is how it is supposed to happen: use asterisk "*" as the instance-length. Omit the content-length header and send Transfer-Encoding: chunked.

Upvotes: 2

Related Questions