Re: Multiple Content-Location headers

jg@pa.dec.com (Jim Gettys) writes:

>To quote from section 4.2 of the HTTP spec:
>
>"Multiple message-header fields with the same field-name may be present in
>a message if and only if the entire field-value for that header field is
>defined as a comma-separated list [i.e., #(values)]. It MUST be possible
>to combine the multiple header fields into one "field-name: field-value"
>pair, without changing the semantics of the message, by appending each
>subsequent field-value to the first, each separated by a comma.

And to add from the long-expired-but-still-regarded-as-authoritative
CGI Internet Draft (draft-robinson-www-interface-01.txt, 15 February
1996) in section 5 "Environment Variables" (pp. 8):

   "If multiple headers with the same field-name are received then
   they must be rewritten as a single header having the same
   semantics."

Not only must it be *possible* to normalize headers, when running a CGI
program all headers *must* be normalized for its pool of variables.

Ross Patterson
Sterling Software, Inc.
VM Software Division