分块编码和内容长度标题 [英] Chunked encoding and content-length header

问题描述

是否可以设置内容长度标题并使用分块传输编码？并且这样做解决了在使用分块时不知道客户端响应的长度的问题？

我正在考虑的情况是当您有大文件传输，确定其大小没有问题，但它太大，无法完全缓冲。
（如果你没有使用分块，那么整个响应必须首先缓冲？）？

谢谢。

解决方案

1）否：消息不能同时包含Content-Length头字段和非身份传输编码，如果消息中包含非-identity transfer-coding，内容长度必须被忽略。 （ RFC 2616，第4.4节）

2）不，你可以使用Content-Length和stream;该协议不会限制您的实现如何工作。

Is it possible to set the content-length header and also use chunked transfer encoding? and does doing so solve the problem of not knowing the length of the response at the client side when using chunked?

the scenario I'm thinking about is when you have a large file to transfer and there's no problem in determining its size, but it's too large to be buffered completely. (If you're not using chunked, then the whole response must get buffered first? Right??)

thanks.

解决方案

1) No: "Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity transfer-coding, the Content-Length MUST be ignored." (RFC 2616, Section 4.4)

2) And no, you can use Content-Length and stream; the protocol doesn't constrain how your implementation works.

这篇关于分块编码和内容长度标题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！