#434: mention in header field considerations that leading/trailing WS is lossy

Julian Reschke <julian.reschke@gmx.de> Tue, 19 February 2013 13:01 UTC

Resent-Date: Tue, 19 Feb 2013 13:00:03 +0000
Resent-Message-Id: <E1U7mnj-0004Gl-BQ@frink.w3.org>
Message-ID: <51237724.3070005@gmx.de>
Date: Tue, 19 Feb 2013 13:59:16 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Received-SPF: pass client-ip=212.227.17.20; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
Subject: #434: mention in header field considerations that leading/trailing WS is lossy
Archived-At: <http://www.w3.org/mid/51237724.3070005@gmx.de>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

...thus this needs to be considered when defining new header fields (-> 
quoted-string).

See < 
http://stackoverflow.com/questions/14910794/value-starting-with-a-space-in-httpurlconnection-add-request-property>

Proposed patch (see 
<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/434/>): 
add the paragraph:

 >  Leading and trailing whitespace in field values is removed upon field
 >  parsing (Section 3.2.4 of [Part1]).  Field definitions where leading
 >  or trailing whitespace in values is significant will have to use a
 >  syntax such as in the quoted-string ABNF production.

Best regards, Julian

#434: mention in header field considerations that… Julian Reschke