Post 请求重组的 TCP 段大于 content-length
Post Request reassembled TCP segment greater than content-length
我用 wireshark 来检查 post 请求,我发现重组后的 TCP 段大小大于 content-length ,因为 content-length 是 [=19 的大小=] 只有?并且 ressambled 包括 header ?
[3 Reassembled TCP Segments (1664 bytes): #1233(578), #1235(1028), #1237(58)]
[Frame: 1233, payload: 0-577 (578 bytes)]
[Frame: 1235, payload: 578-1605 (1028 bytes)]
[Frame: 1237, payload: 1606-1663 (58 bytes)]
[Segment count: 3]
[Reassembled TCP length: 1664]
Hypertext Transfer Protocol
content-length: 1249\r\n
is that because content-length is for the size of body only
正确。 Content-length 仅描述消息的长度 body。来自 the HTTP standard:
14.13 Content-Length
The Content-Length entity-header field indicates the size of the entity-body, in decimal number of OCTETs ...
... and the ressambled includes the header ?
鉴于您显示了重组数据中包含的 header 的一部分,这些数据显然至少包含 header.
的一部分
我用 wireshark 来检查 post 请求,我发现重组后的 TCP 段大小大于 content-length ,因为 content-length 是 [=19 的大小=] 只有?并且 ressambled 包括 header ?
[3 Reassembled TCP Segments (1664 bytes): #1233(578), #1235(1028), #1237(58)]
[Frame: 1233, payload: 0-577 (578 bytes)]
[Frame: 1235, payload: 578-1605 (1028 bytes)]
[Frame: 1237, payload: 1606-1663 (58 bytes)]
[Segment count: 3]
[Reassembled TCP length: 1664]
Hypertext Transfer Protocol
content-length: 1249\r\n
is that because content-length is for the size of body only
正确。 Content-length 仅描述消息的长度 body。来自 the HTTP standard:
14.13 Content-Length
The Content-Length entity-header field indicates the size of the entity-body, in decimal number of OCTETs ...
... and the ressambled includes the header ?
鉴于您显示了重组数据中包含的 header 的一部分,这些数据显然至少包含 header.
的一部分