简述HTTP 协议接收Message Body的方式

最新推荐文章于 2022-08-31 15:41:54 发布

HuaHuaXia

最新推荐文章于 2022-08-31 15:41:54 发布

阅读量4k

点赞数

分类专栏： HTTP

本文链接：https://blog.csdn.net/HuaHuaXia/article/details/53557505

版权

HTTP消息体的长度由优先级条件决定：1. 没有消息体的响应；2. 使用非'identity'的Transfer-Encoding；3. Content-Length字段；4.multipart/byteranges媒体类型；5. 服务器关闭连接。Accept-Ranges头指示服务器是否接受字节范围请求。Range头用于请求资源的特定部分，Content-Range头在206响应中指示实际传输的字节范围。

摘要由CSDN通过智能技术生成

HTTP Message Length 消息长度

如下是HTTP协议中关于Message Length的英文原文：

4.4 Message Length

The transfer-length of a message is the length of the message-body as it appears in the message; that is, after any transfer-codings have been applied. When a message-body is included with a message, the transfer-length of that body is determined by one of the following (in order of precedence):

1.Any response message which “MUST NOT” include a message-body (such as the 1xx, 204, and 304 responses and any response to a HEAD request) is always terminated by the first empty line after the header fields, regardless of the entity-header fields present in the message.

2.If a Transfer-Encoding header field (section 14.41) is present and has any value other than “identity”, then the transfer-length is defined by use of the “chunked” transfer-coding (section 3.6), unless the message is terminated by closing the connection.

3.If a Content-Length header field (section 14.13) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header field MUST NOT be sent if these two lengths are different (i.e., if a Transfer-Encoding
header field is present). If a message is received with both a
Transfer-Encoding header field and a Content-Length header field,
the latter MUST be ignored.
4.If the message uses the media type “multipart/byteranges”, and the transfer-length is not otherwise specified, then this self- delimiting media type defines the transfer-length. This media type MUST NOT be used unless the sender knows that the recipient can parse it; the presence in a request of a Range header with multiple byte- range specifiers from a 1.1 client implies that the client can parse multipart/byteranges responses.