Skip to content

Commit

Permalink
doc: message.header duplication correction
Browse files Browse the repository at this point in the history
The old version of the text here was slightly incorrect, so it
just defers the details to the section in which they're fully
described.

PR-URL: #3997
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
  • Loading branch information
bengl authored and rvagg committed Dec 5, 2015
1 parent dd0d15f commit f0a2e2c
Showing 1 changed file with 2 additions and 5 deletions.
7 changes: 2 additions & 5 deletions doc/api/http.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,7 @@ HTTP API is very low-level. It deals with stream handling and message
parsing only. It parses a message into headers and body but it does not
parse the actual headers or the body.

Defined headers that allow multiple values are concatenated with a `,`
character, except for the `set-cookie` and `cookie` headers which are
represented as an array of values. Headers such as `content-length`
which can only have a single value are parsed accordingly, and only a
single value is represented on the parsed object.
See [message.headers][] for details on how duplicate headers are handled.

The raw headers as they were received are retained in the `rawHeaders`
property, which is an array of `[key, value, key2, value2, ...]`. For
Expand Down Expand Up @@ -1083,6 +1079,7 @@ There are a few special headers that should be noted.
* Sending an Authorization header will override using the `auth` option
to compute basic authentication.

[message.headers][]: #http_message_headers
[constructor options]: #http_new_agent_options
[`destroy()`]: #http_agent_destroy
['checkContinue']: #http_event_checkcontinue
Expand Down

0 comments on commit f0a2e2c

Please sign in to comment.