Re: Translating CR LF to HTTP/1 headers

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