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

Re: Translating CR LF to HTTP/1 headers

From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Thu, 5 Sep 2013 01:20:49 +0900
Message-ID: <CAPyZ6=KBJ0SqwpB4EsaF1Yyx1_K+NubLhP+FBUDYpaMoBpASZQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Thank you for the clarification. How about clearly state that U+000D and
U+000A in header field must be replaced with U+0020 in that section? It
will spare the time for the readers to go around and check obs-fold
production.
Just like this:

"""
...
In particular, header field names or values that contain characters not
permitted by HTTP/1.1, including carriage return (U+000D) or line feed
(U+000A) MUST NOT be translated verbatim.
The carriage return (U+000D) and line feed (U+000A) in header field values
are considered instances of the obs-fold production and MUST be replaced
with space (U+0020).
"""

Best regards,

Tatsuhiro Tsujikawa


On Wed, Sep 4, 2013 at 8:45 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 3 September 2013 16:40, Manger, James H
> <James.H.Manger@team.telstra.com> wrote:
> > “…carriage return (U+000D) or line feed (U+000A)…”
>
> Yeah, my bad.  Fixed.
>
>
Received on Wednesday, 4 September 2013 16:21:36 UTC

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