diff options
author | Fedor Indutny <fedor@indutny.com> | 2014-09-13 13:08:25 +0100 |
---|---|---|
committer | Timothy J Fontaine <tjfontaine@gmail.com> | 2014-09-16 15:24:19 -0700 |
commit | 1fddc1fee84785d296e37337dcb0dc12c13a049f (patch) | |
tree | 92eac4663cbfabd1476e20c63e32935904d01dd4 /deps/npm/lib/utils/error-handler.js | |
parent | 6e689ece46726f39bdf93f1f35e01656f8fe27dc (diff) | |
download | node-1fddc1fee84785d296e37337dcb0dc12c13a049f.tar.gz |
http: do not send `0\r\n\r\n` in TE HEAD responses
When replying to a HEAD request, do not attempt to send the trailers and
EOF sequence (`0\r\n\r\n`). The HEAD request MUST not have body.
Quote from RFC:
The presence of a message body in a response depends on both the
request method to which it is responding and the response status code
(Section 3.1.2). Responses to the HEAD request method (Section 4.3.2
of [RFC7231]) never include a message body because the associated
response header fields (e.g., Transfer-Encoding, Content-Length,
etc.), if present, indicate only what their values would have been if
the request method had been GET (Section 4.3.1 of [RFC7231]).
fix #8361
Reviewed-By: Timothy J Fontaine <tjfontaine@gmail.com>
Diffstat (limited to 'deps/npm/lib/utils/error-handler.js')
0 files changed, 0 insertions, 0 deletions