W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Translating CR LF to HTTP/1 headers

From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Wed, 4 Sep 2013 00:31:27 +0900
Message-ID: <CAPyZ6=LAboOUxCSYqg3wT_abqLdmr3Z6YemXQWvzT+ZpA8mgGA@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
In http://http2.github.io/http2-spec/#rfc.section.10.3

An intermediary that performs translation into HTTP/1.1 cannot
alter the semantics of requests or responses. In particular,
header field names or values that contain characters not
permitted by HTTP/1.1, including carriage return (U+10) or line
feed (U+13) MUST NOT be translated verbatim.

So if U+10 and/or U+13 are included in HTTP/2 headers, what
should intermediary do to translate them into HTTP/1?  Just
remove them or replace them with safe characters? The meaning of
the headers may change with these changes, especially if those
characters are permitted in HTTP/2 headers.  Returning 5xx
response may be an option. But there is very interesting
situation. If all machines in the path are HTTP/2, then the
request succeeds, but if one of them is HTTP/1 then request

Best regards,

Tatsuhiro Tsujikawa
Received on Tuesday, 3 September 2013 15:32:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:15 UTC