net/http: fix Response.Header documentation for multiple headers with same key

Whether the keys are concatenated or separate (or a mixture) depends on the server.

Fixes #5979.

R=golang-dev, bradfitz
CC=golang-dev
https://golang.org/cl/12433043

diff --git a/src/pkg/net/http/response.go b/src/pkg/net/http/response.go
index 0d7c8248a7edf973790822d8030675bb2d876665..30d785f541356163dc78830dd5a0d6b91ee3eccd 100644 (file)
--- a/src/pkg/net/http/response.go
+++ b/src/pkg/net/http/response.go
@@ -32,7 +32,7 @@ type Response struct {
        ProtoMinor int    // e.g. 0
 
        // Header maps header keys to values.  If the response had multiple
-       // headers with the same key, they will be concatenated, with comma
+       // headers with the same key, they may be concatenated, with comma
        // delimiters.  (Section 4.2 of RFC 2616 requires that multiple headers
        // be semantically equivalent to a comma-delimited sequence.) Values
        // duplicated by other fields in this struct (e.g., ContentLength) are