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

Only because parameters are ill-defined (something we're fixing in  

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  


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

> On Sun, Jul 12, 2009 at 4:45 PM, Mark Nottingham<> 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

Received on Monday, 13 July 2009 00:26:48 UTC