package h1
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=b851d170d99f1e216674c00c2a24b92a2948c0cca57ff0282427f1965ac8bd13
sha512=dde55fc1e6c6615c6b2a8baca1273528b305dd9f15e6bcb4a283b5f0e7909c7be549dd1ce802eceab2404eeb81def9f9350fe31b8a76ae65a004008dd6865e71
doc/h1/H1/Headers/index.html
Module H1.Headers
Source
Header Fields
Each header field consists of a case-insensitive field name and a field value. The order in which header fields with differing field names are received is not significant. However, it is good practice to send header fields that contain control data first so that implementations can decide when not to handle a message as early as possible.
A sender MUST NOT generate multiple header fields with the same field name in a message unless either the entire field value for that header field is defined as a comma-separated list or the header field is a well-known exception, e.g., Set-Cookie
.
A recipient MAY combine multiple header fields with the same field name into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field value to the combined field value in order, separated by a comma. The order in which header fields with the same field name are received is therefore significant to the interpretation of the combined field value; a proxy MUST NOT change the order of these field values when forwarding a message.
Note. Unless otherwise specified, all operations preserve header field order and all reference to equality on names is assumed to be case-insensitive.
See RFC7230§3.2 for more details.
Case-insensitive equality for testing header names or values