walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Document that libnghttp2's behaviour about Content-Length

This commit is contained in:
Tatsuhiro Tsujikawa 2016-11-03 23:09:30 +09:00
parent 6eb2829ee8
commit c171097dea
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/programmers-guide.rst
View File

@ -173,6 +173,11 @@ parsed as 64 bit signed integer. The sum of data length in the
following DATA frames must match with the number in "Content-Length" following DATA frames must match with the number in "Content-Length"
header field if it is present (this does not include padding bytes). header field if it is present (this does not include padding bytes).
RFC 7230 says that server must not send "Content-Length" in any
response with 1xx, and 204 status code. It also says that
"Content-Length" is not allowed in any response with 200 status code
to a CONNECT request. nghttp2 enforces them as well.
Any deviation results in stream error of type PROTOCOL_ERROR. If Any deviation results in stream error of type PROTOCOL_ERROR. If
error is found in PUSH_PROMISE frame, stream error is raised against error is found in PUSH_PROMISE frame, stream error is raised against
promised stream. promised stream.