-
Notifications
You must be signed in to change notification settings - Fork 30k
Commit
This commit documents how duplicate HTTP headers are handled. PR-URL: #3810 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -816,6 +816,16 @@ Example: | |
// accept: '*/*' } | ||
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`, | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
sam-github
Contributor
|
||
`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 | ||
|
||
In case of server request, the HTTP version sent by the client. In the case of | ||
|
Where is the spec describing that these headers should be discarded when duplicate?