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

Re: Comments on the HTTP Sec-From Header (draft-abarth-origin)

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 13 Jul 2009 10:25:35 +1000
Cc: Ian Hickson <ian@hixie.ch>, "collinj@cs.stanford.edu" <collinj@cs.stanford.edu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <DF20E4D9-C670-4146-BEB7-EDA9C735D366@mnot.net>
To: Adam Barth <w3c@adambarth.com>
Only because parameters are ill-defined (something we're fixing in  
HTTPbis).

Any format can have parsing errors; e.g., as soon as someone finds a  
way to get a space into the header you've defined, it's going to be an  
issue.

Cheers,


On 13/07/2009, at 9:57 AM, Adam Barth wrote:

> On Sun, Jul 12, 2009 at 4:45 PM, Mark Nottingham<mnot@mnot.net> wrote:
>> That perspective is understandable, if you're starting from a clean  
>> slate.
>>  From where I sit, every time somebody adds a new type of syntax, new
>> parsing code has to be written, increasing the chance of errors. It  
>> also
>> means that people have to learn yet another specialized syntax  
>> rather than
>> leveraging existing knowledge.
>
> The quotes are kind of disaster, no?  What if we see single quotes?
> What if the quotes aren't there?  These kinds of issues have plagued
> the Content-Type header.
>
> Adam


--
Mark Nottingham     http://www.mnot.net/
Received on Monday, 13 July 2009 00:26:48 GMT

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