]> The Varnish Cache Project

phk@varnish-cache.org

Applications and Real-Time HTTP Internet-Draft An abstract data model for HTTP headers, “Common Structure”, and a HTTP/1 serialization of it, generalized from current HTTP headers. Discussion of this draft takes place on the HTTP working group mailing list (ietf-http-wg@w3.org), which is archived at https://lists.w3.org/Archives/Public/ietf-http-wg/. Working Group information can be found at http://httpwg.github.io/; source code and issues list for this draft can be found at https://github.com/httpwg/http-extensions/labels/header-structure.

The HTTP protocol does not impose any structure or datamodel on the information in HTTP headers, the HTTP/1 serialization is the datamodel: An ASCII string without control characters. HTTP header definitions specify how the string must be formatted and while families of similar headers exist, it still requires an uncomfortable large number of bespoke parser and validation routines to process HTTP traffic correctly. In order to improve performance HTTP/2 and HPACK uses naive text-compression, which incidentally decoupled the on-the-wire serialization from the data model. During the development of HPACK it became evident that significantly bigger gains were available if semantic compression could be used, most notably with timestamps. However, the lack of a common data structure for HTTP headers would make semantic compression one long list of special cases. Parallel to this, various proposals for how to fulfill data-transportation needs, and to a lesser degree to impose some kind of order on HTTP headers, at least going forward, were floated. All of these proposals, JSON, CBOR etc. run into the same basic problem: Their serialization is incompatible with RFC 7230’s ABNF definition of ‘field-value’. For binary formats, such as CBOR, a wholesale base64/85 reserialization would be needed, with negative results for both debugability and bandwidth. For textual formats, such as JSON, the format must first be neutered to not violate field-value’s ABNF, and then workarounds added to reintroduce the features just lost, for instance UNICODE strings. The post-surgery format is no longer JSON, and it experience indicates that almost-but-not-quite compatibility is worse than no compatibility. This proposal starts from the other end, and builds and generalizes a data structure definition from existing HTTP headers, which means that HTTP/1 serialization and ‘field-value’ compatibility is built in. If all future HTTP headers are defined to fit into this Common Structure we have at least halted the proliferation of bespoke parsers and started to pave the road for semantic compression serializations of HTTP traffic.

In this document, the key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” are to be interpreted as described in BCP 14, RFC 2119 .

The data model of Common Structure is an ordered sequence of named dictionaries. Please see for how this model was derived. The definition of the data model is on purpose abstract, uncoupled from any protocol serialization or programming environment representation, it is meant as the foundation on which all such manifestations of the model can be built. Common Structure in ABNF (Slightly bastardized relative to RFC5234 ):

Recursion is included as a way to to support deep and more general data structures, but its use is highly discouraged and where it is used the depth of recursion SHALL always be explicitly limited in the specifications of the HTTP headers which allow it.

Integers SHALL be in the range +/- 2^63-1 (= +/- 9223372036854775807)

The limit of 15 significant digits is chosen so that numbers can be correctly represented by IEEE754 64 bit binary floating point.

This is intended to be an efficient, “safe” and uncomplicated string type, for uses where the string content is culturally neutral or where it will not be user visible.

# UNICODE nicked from draft-seantek-unicode-in-abnf-02 ]]>

Unicode-strings are unrestricted because there is no sane and/or culturally neutral way to subset or otherwise make unicode “safe”, and Unicode is still evolving new and interesting code points. Users of unicode-string SHALL be prepared for the full gammut of glyph-gymnastics in order to avoid U+1F4A9 U+08 U+1F574.

Blobs are intended primarily for cryptographic data, but can be used for any otherwise unsatisfied needs.

A timestamp counts seconds since the UNIX time_t epoch, including the “invisible leap-seconds” misfeature.

In ABNF:

Only white-listed legacy headers (see ) can use this format.

" h1-common-structure "<" h1-common-structure = h1-element * ("," h1-element) h1-element = identifier * (";" identifier ["=" h1-value]) h1-value = identifier / integer / number / h1-ascii-string / h1-unicode-string / h1-blob / h1-timestamp / ">" h1-common-structure "<" h1-ascii-string = DQUOTE *( ( "\" DQUOTE ) / ( "\" "\" ) / 0x20-21 / 0x23-5B / 0x5D-7E ) DQUOTE h1-unicode-string = DQUOTE *( ( "\" DQUOTE ) ( "\" "\" ) / EmbeddedUnicodeChar / 0x20-21 / 0x23-5B / 0x5D-7E / ) DQUOTE ]]>

The dim prospects of ever getting a majority of HTTP1 paths 8-bit clean makes UTF-8 unviable as H1 serialization. Given that very little of the information in HTTP headers is presented to users in the first place, improving H1 and HPACK efficiency by inventing a more efficient RFC5137 compliant escape-sequences seems unwarranted.

XXX: Allow OWS in parsers, but not in generators ? In programming environments which do not define a native representation or serialization of Common Structure, the HTTP/1 serialization should be used.

All future standardized and all private HTTP headers using Common Structure should self identify as such. In the HTTP/1 serialization by making the first character “>” and the last “<”. (These two characters are deliberately “the wrong way” to not clash with exsisting usages.) Legacy HTTP headers which fit into Common Structure, are marked as such in the IANA Message Header Registry (see ), and a snapshot of the registry can be used to trigger parsing according to Common Structure of these headers.

All new HTTP headers SHOULD use the Common Structure if at all possible.

Should we allow splitting common structure data over multiple headers ? Pro: Avoids size restrictions, easier on-the-fly editing Contra: Cannot act on any such header until all headers have been received. We must define where headers can be split (between identifier and dictionary ?, in the middle of dictionaries ?) Most on-the-fly editing is hackish at best.

The HTTP/1 serializations self-identification mechanism makes it possible to extend the definition of existing headers into Common Structure. For instance one could imagine:

1475061449.201< ]]>

Which would be faster to parse and validate than the current definition of the Date header and more precise too. Some kind of signal/negotiation mechanism would be required to make this work in practice.

A machine-readable specification of the legal contents of HTTP headers would go a long way to improve efficiency and security in HTTP implementations.

The IANA Message Header Registry will be extended with an additional field named “Common Structure” which can have the values “True”, “False” or “Unknown”. The RFC723x headers listed in will get the value “True” in the new field. The RFC723x headers listed in will get the value “False” in the new field. All other existing entries in the registry will be set to “Unknown” until and if the owner of the entry requests otherwise.

Unique dictionary keys are required to reduce the risk of smuggling attacks.

&RFC2119; &RFC5137; &RFC5234; &RFC7230; &RFC7231; &RFC7232; &RFC7233; &RFC7234; &RFC7235; &RFC7239; &RFC7694;

Several proposals have been floated in recent years to use some preexisting structured data serialization or other for HTTP headers, to impose some sanity. None of these proposals have gained traction and no obvious candidate data serializations have been left unexamined. This effort tries to tackle the question from the other side, by asking if there is a common structure in existing HTTP headers we can generalize for this purpose.

The RFC723x family of HTTP/1 standards control 49 entries in the IANA Message Header Registry, and they share two common motifs. The majority of RFC723x HTTP headers are lists. A few of them are ordered, (‘Content-Encoding’), some are unordered (‘Connection’) and some are ordered by ‘q=%f’ weight parameters (‘Accept’) In most cases, the list elements are some kind of identifier, usually derived from ABNF ‘token’ as defined by . A subgroup of headers, mostly related to MIME, uses what one could call a ‘qualified token’::

The second motif is parameterized list elements. The best known is the “q=0.5” weight parameter, but other parameters exist as well. Generalizing from these motifs, our candidate “Common Structure” data model becomes an ordered list of named dictionaries. In pidgin ABNF, ignoring white-space for the sake of clarity, the HTTP/1.1 serialization of Common Structure is is something like:

Nineteen out of the RFC723x’s 48 headers, almost 40%, can already be parsed using this definition, and none the rest have requirements which could not be met by this data model. See and for the full survey details.

Surveying the datatypes of HTTP headers, standardized as well as private, the following picture emerges:

Integer and floating point are both used. Range and precision is mostly unspecified in controlling documents. Scientific notation (9.192631770e9) does not seem to be used anywhere. The ranges used seem to be minus several thousand to plus a couple of billions, the high end almost exclusively being POSIX time_t timestamps.

RFC723x text format, but POSIX time_t represented as integer or floating point is not uncommon. ISO8601 have also been spotted.

The vast majority are pure ASCII strings, with either no escapes, %xx URL-like escapes or C-style back-slash escapes, possibly with the addition of \uxxxx UNICODE escapes. Where non-ASCII character sets are used, they are almost always implicit, rather than explicit. UTF8 and ISO-8859-1 seem to be most common.

Often used for cryptographic data. Usually in base64 encoding, sometimes ““-quoted more often not. base85 encoding is also seen, usually quoted.

Seems to almost always fit in the RFC723x ‘token’ definition.

The number one wishlist item seems to be UNICODE strings, with a big side order of not having to write a new parser routine every time somebody comes up with a new header. Having a common parser would indeed be a good thing, and having an underlying data model which makes it possible define a compressed serialization, rather than rely on serialization to text followed by text compression (ie: HPACK) seems like a good idea too. However, when using a datamodel and a parser general enough to transport useful data, it will have to be followed by a validation step, which checks that the data also makes sense. Today validation, such as it is, is often done by the bespoke parsers. This then is probably where the next big potential for improvement lies: Ideally a machine readable “data dictionary” which makes it possibly to copy that text out of RFCs, run it through a code generator which spits out validation code which operates on the output of the common parser. But history has been particularly unkind to that idea. Most attempts studied as part of this effort, have sunk under complexity caused by reaching for generality, but where scope has been wisely limited, it seems to be possible. So file that idea under “future work”.

Accept , Section 5.3.2 Accept-Charset , Section 5.3.3 Accept-Encoding , Section 5.3.4, , Section 3 Accept-Language , Section 5.3.5 Age , Section 5.1 Allow , Section 7.4.1 Connection , Section 6.1 Content-Encoding , Section 3.1.2.2 Content-Language , Section 3.1.3.2 Content-Length , Section 3.3.2 Content-Type , Section 3.1.1.5 Expect , Section 5.1.1 Max-Forwards , Section 5.1.2 MIME-Version , Appendix A.1 TE , Section 4.3 Trailer , Section 4.4 Transfer-Encoding , Section 3.3.1 Upgrade , Section 6.7 Vary , Section 7.1.4

1 of the RFC723x headers is only reserved, and therefore have no structure at all: Close , Section 8.1 5 of the RFC723x headers are HTTP dates: Date , Section 7.1.1.2 Expires , Section 5.3 If-Modified-Since , Section 3.3 If-Unmodified-Since , Section 3.4 Last-Modified , Section 2.2 24 of the RFC723x headers use bespoke formats which only a single or in rare cases two headers share: Accept-Ranges , Section 2.3 bytes-unit / other-range-unit Authorization , Section 4.2 Proxy-Authorization , Section 4.4 credentials Cache-Control , Section 5.2 1#cache-directive Content-Location , Section 3.1.4.2 absolute-URI / partial-URI Content-Range , Section 4.2 byte-content-range / other-content-range ETag , Section 2.3 entity-tag Forwarded 1#forwarded-element From , Section 5.5.1 mailbox If-Match , Section 3.1 If-None-Match , Section 3.2 “*” / 1#entity-tag If-Range , Section 3.2 entity-tag / HTTP-date Host , Section 5.4 uri-host [ “:” port ] Location , Section 7.1.2 URI-reference Pragma , Section 5.4 1#pragma-directive Range , Section 3.1 byte-ranges-specifier / other-ranges-specifier Referer , Section 5.5.2 absolute-URI / partial-URI Retry-After , Section 7.1.3 HTTP-date / delay-seconds Server , Section 7.4.2 User-Agent , Section 5.5.3 product *( RWS ( product / comment ) ) Via , Section 5.7.1 1#( received-protocol RWS received-by [ RWS comment ] ) Warning , Section 5.5 1#warning-value Proxy-Authenticate , Section 4.3 WWW-Authenticate , Section 4.1 1#challenge

Added signed 64bit integer type. Drop UTF8, and settle on BCP137 ::EmbeddedUnicodeChar for h1-unicode-string. Change h1_blob delimiter to “:” since “’” is valid t_char