IETF Logo Mail Archive

Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt

Julian Reschke <julian.reschke@gmx.de> Fri, 22 January 2010 09:02 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87F823A68AA for <apps-discuss@core3.amsl.com>; Fri, 22 Jan 2010 01:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level:
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZifkVDbTesd for <apps-discuss@core3.amsl.com>; Fri, 22 Jan 2010 01:02:28 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 534B03A6835 for <discuss@apps.ietf.org>; Fri, 22 Jan 2010 01:02:27 -0800 (PST)
Received: (qmail invoked by alias); 22 Jan 2010 09:02:20 -0000
Received: from p508FD092.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.208.146] by mail.gmx.net (mp057) with SMTP; 22 Jan 2010 10:02:20 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/2I3deK2P2JxXm8RxJgwTgf+r4GPEGoCixzUBhCJ aBPPc169mveJ2I
Message-ID: <4B59698C.60105@gmx.de>
Date: Fri, 22 Jan 2010 10:02:04 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
References: <20100119053002.5CD613A683B@core3.amsl.com> <E4FF7733-D744-4AC3-AB99-66A12868E4CE@mnot.net> <4B56E27D.800@gmx.de> <4B585B06.1040704@gmx.de> <7a2269961001210701t15ea51cdmf48cc696282c44b6@mail.gmail.com> <4B586DF0.9010201@gmx.de> <A190150C-D5AC-467B-A665-64B9859E256F@mnot.net>
In-Reply-To: <A190150C-D5AC-467B-A665-64B9859E256F@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.70999999999999996
Cc: Apps Discuss <discuss@apps.ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, mjb@asplake.co.uk
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2010 09:02:29 -0000

Mark Nottingham wrote:
> I agree in principle, but practically, it's almost a foregone conclusion that people will produce these unquoted, and implementations will consume them happily. I'd rather align with what is done in practice, even if it does preclude using a generic parser...
> ...

I just did some testing with the two UAs I have that actually do 
something the the Link header; Firefox and Opera.

Both process the type parameter both quoted and unquoted. So minimally 
the ABNF should allow both.

That being said, given the little amount of deployment, I'd *much* 
prefer to make the ABNF consistent with generic parameter parsing, and 
potentially just add a statement that unquoted type parameters may occur 
in the wild (*) and may have to be accepted as well.

Best regards, Julian

(*) do they, outside of test cases?

v2.36.0 | Report a Bug | By Email | System Status