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

p1: BWS

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 18 Apr 2013 11:18:22 +1000
Message-Id: <DB8598D0-7AD8-4A90-806B-E4C7B65118D7@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
p1 3.2.3 says:

>    BWS is used where the grammar allows optional whitespace, for
>    historical reasons, but senders SHOULD NOT generate it in messages;
>    recipients MUST accept such bad optional whitespace and remove it
>    before interpreting the field value or forwarding the message
>    downstream.

  http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-22#section-3.2.3

Throughout our specs, BWS is used at the end of header fields:
     header-field   = field-name ":" OWS field-value BWS

and in transfer-codings:
     transfer-parameter = attribute BWS "=" BWS value

and in Expect headers:
  expectation  = expect-name [ BWS "=" BWS expect-value]
                             *( OWS ";" [ OWS expect-param ] )
  expect-param = expect-name [ BWS "=" BWS expect-value ]

and, finally, in auth-params on challenges and credentials:
  auth-param     = token BWS "=" BWS ( token / quoted-string )

Is this whitespace really "bad" enough to MUST-require that intermediaries (including load balancers and other hardware!) remove it before forwarding the message?

Cheers,

--
Mark Nottingham   http://www.mnot.net/
Received on Thursday, 18 April 2013 01:18:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC