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

Re: Proposal: i67 - quoting charsets

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 11 Apr 2008 11:23:04 +1000
Cc: Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <ECEE9DA7-00D8-46AF-B35F-0114CB90DFC1@mnot.net>
To: Henrik Nordstrom <henrik@henriknordstrom.net>

Hmm. That's the opposite of the direction I *thought* we were going in.

If a parameter specifies a token, e.g., charset, I read the discussion  
as saying that we should also accept a quoted-string. This allows the  
approach that Frank was talking about (quote everything, just for  
safety and simplicity's sake).

If a parameter specifies a quoted-string, there isn't any  
corresponding rationale to support also allowing a token.

That's why I wrote the proposal as I did.


On 11/04/2008, at 10:33 AM, Henrik Nordstrom wrote:

>
> tor 2008-04-10 klockan 17:17 +0200 skrev Julian Reschke:
>
>> I have my doubts. Why add special cases in producers when it's not
>> needed? Or *are* special cases needed?
>
> I wouldn't expect all parsers to deal with quoted parameters in all
> cases.. the current specs is a bit fuzzy on that.
>
> But I do expect the ones who deal with quoted parameters to also  
> handle
> the token form..
>
> Regards
> Henrik
>
>
>
>


--
Mark Nottingham     http://www.mnot.net/
Received on Friday, 11 April 2008 01:24:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:47 GMT