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

Re: RFC2231 encoding in HTTP: whitespace handling

From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Thu, 28 Aug 2008 10:20:56 +0000
Message-ID: <050701c908f7$fad076c0$41fb52d4@xyzzy>
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: <ietf-http-wg@w3.org>

Julian Reschke wrote:

> Can you point to language or ABNF rules in RFC2231 or MIME
> that actually says that (I'm ready to believe you, I just
> want to understand how you come to that conclusion...).

It's a bit tricky, that's why I sent a copy to Ned.

"*" is no <tspecials> in RFC 2045.  A lexical parser handles
it as ordinary token character.

"*" is also no <specials> in RFC 5232 (2822upd).  A lexical
parser handles it as ordinary <atext> character.

RFC 2231 does not update <tspecials>.  In fact it says:

| Specifically, an asterisk at the end of a parameter name
| acts as an indicator that character set and language
| information may appear at the beginning of the parameter
| value.

"At the end of" is arguably not the same as "following".
Not the same situation as for "=", where RFC 2045 states:

| Note that the definition of "tspecials" is the same as
| the RFC 822 definition of "specials" with the addition
| of the three characters "/", "?", and "=", and the
| removal of ".".

But I'm far from sure that my interpretation is okay...

Received on Thursday, 28 August 2008 12:44:18 UTC

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