Browse Source

doc: clarify duplicate header handling

This commit documents how duplicate HTTP headers are handled.

PR-URL: https://github.com/nodejs/node/pull/3810
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
v5.x
Bryan English 9 years ago
committed by Jeremiah Senkpiel
parent
commit
25c3807051
  1. 10
      doc/api/http.markdown

10
doc/api/http.markdown

@ -816,6 +816,16 @@ Example:
// accept: '*/*' } // accept: '*/*' }
console.log(request.headers); console.log(request.headers);
Duplicates in raw headers are handled in the following ways, depending on the
header name:
* Duplicates of `age`, `authorization`, `content-length`, `content-type`,
`etag`, `expires`, `from`, `host`, `if-modified-since`, `if-unmodified-since`,
`last-modified`, `location`, `max-forwards`, `proxy-authorization`, `referer`,
`retry-after`, or `user-agent` are discarded.
* `set-cookie` is always an array. Duplicates are added to the array.
* For all other headers, the values are joined together with ', '.
### message.httpVersion ### message.httpVersion
In case of server request, the HTTP version sent by the client. In the case of In case of server request, the HTTP version sent by the client. In the case of

Loading…
Cancel
Save