Connected: An Internet Encyclopedia
RFC 1945 - 4.2 Message Headers

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: 4. HTTP Message
Prev: 4.1 Message Types
Next: 4.3 General Header Fields

### 4.2 Message Headers

HTTP header fields, which include General-Header (Section 4.3), Request-Header (Section 5.2), Response-Header (Section 6.2), and Entity-Header (Section 7.1) fields, follow the same generic format as that given in Section 3.1 of RFC 822 [7]. Each header field consists of a name followed immediately by a colon (":"), a single space (SP) character, and the field value. Field names are case-insensitive. Header fields can be extended over multiple lines by preceding each extra line with at least one SP or HT, though this is not recommended.

           HTTP-header    = field-name ":" [ field-value ] CRLF

           field-name     = token
           field-value    = *( field-content | LWS )

           field-content  = <the OCTETs making up the field-value
                            and consisting of either *TEXT or combinations
                            of token, tspecials, and quoted-string>

The order in which header fields are received is not significant. However, it is "good practice" to send General-Header fields first, followed by Request-Header or Response-Header fields prior to the Entity-Header fields.

Multiple HTTP-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.

Next: 4.3 General Header Fields

Connected: An Internet Encyclopedia
RFC 1945 - 4.2 Message Headers