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

Question

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

npnmodp · Accepted Answer · 2020-04-14 20:45:24Z

2

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.

edited Apr 14, 2020 at 20:45

answered Jul 26, 2014 at 3:22

npnmodp

1,24810 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

user207421 Over a year ago

You mean omit the Content-length header.

npnmodp Over a year ago

From a server point of view, it should omit Content-Length header when sending "Transfer-Encoding: chunked". From a client point of view it can only ignore the Content-Length header in case it is received with a Transfer-Encoding: chunked.

Collectives™ on Stack Overflow

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

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related