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

Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 15 May 2012 07:23:35 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: John Sullivan <jsullivan@velocix.com>, Andreas Petersson <andreas@sbin.se>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Message-ID: <20120515052335.GA8977@1wt.eu>
Hi Julian,

On Mon, May 14, 2012 at 11:55:34PM +0200, Julian Reschke wrote:
> On 2012-05-14 23:48, Willy Tarreau wrote:
> >...
> >OK in theory but in practice I'm fairly sure we'll see IPv6 addresses
> >sent unquoted because a number of implementations will not have noticed
> >they became mandatory. That's why sometimes widening a character set to
> >better fit what it is supposed to represent makes a lot of sense. This
> >can even be done by slightly extending the grammar :
> >
> >    Forwarded-v = 1#( token "=" ( ipv4 / ipv6 / token / quoted-string ) *( 
> >    ";" ... ) )
> >...
> 
> The downside is that you can't use an off-the-shelf parser component, 
> which I believe is a pretty big downside.
> 
> The HTTP community has been inventing new microsyntaxes for many years, 
> and as far as I can tell, most header field parsers out there are broken 
> beyond belief. We need less of them, even if this means that a few edge 
> cases will be more verbose than necessary.

I see, and indeed this is a good point. Considering the number of times
I've heard "hey, your product sends me commas in IP addresses", it is
certain that people don't understand what they retrieve there.

Cheers,
Willy
Received on Tuesday, 15 May 2012 05:25:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 05:25:43 GMT