Are the chunk sizes in an HTTP response with "Transfer-Encoding: chunked", significant to protocols that sit on top of HTTP?

Question

Does anything carried inside HTTP care about chunk sizes? Some sort of RPC protocol perhaps?

EDIT: Here's the Wikipedia sample response

Date: Mon, 30 Mar 2009 22:22:21 GMT

HTTP/1.1 200 OK
Content-Type: text/plain
Transfer-Encoding: chunked

23
This is the data in the first chunk

1A
and this is the second one

0

The response could have easily been chopped up into chunks of sizes different from 23 and 1A. Is there a case where chunk boundaries may be significant?

Answer 1

None that I know of. It would be against the spirit of HTTP if not an outright bug.