doc: clarify duplicate header handling

This commit documents how duplicate HTTP headers are handled. PR-URL: #3810 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
nodejs · Dec 17, 2015 · 6de77cd · 6de77cd
1 parent b22973a
commit 6de77cd
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/doc/api/http.markdown b/doc/api/http.markdown
@@ -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`,
+`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