Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Tim Bray <tbray@textuality.com> Mon, 22 October 2012 23:17 UTC
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA2E11E80FB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3s3hED+SpqRA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:17:30 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 00FBD11E80F4 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so3553465obq.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=wN7gFXNILJCq1rrXHmx2TKbFkrCer5GkCYwh6ffms/I=; b=HbVwMdO299WLkVjsp0EuV2JQ1Is+RfWd6/XS/ZNbyLsfmtkLAWVvfIFRHfgUU+equU bO9xvsunVQua2ZFQF11BXBFAP8n1eVUJlAzZMWYKXShSXMGsGnk+XS5JSgzILEqgEd69 31fR+mJWPYngk5ImFgPrPVn++t+RHlY2yBctOymFb4foITgxhSZBdgEQNjNzPbjsf1fs yEpSmlnVcVnVDcQoNyhVIVsvDfNL9aV/kNJozoTgV7cp0d02iki7BbYqlhl0sdj+EL1B nAenoU0zV+dv131zLDWqG2jUTI6KViqUDfbDs7I4Zs5EpI249RPovTe7PDpQL80XtAJt ba1A==
MIME-Version: 1.0
Received: by 10.60.13.198 with SMTP id j6mr9488477oec.51.1350947849174; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
Received: by 10.76.87.136 with HTTP; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
X-Originating-IP: [2620:0:1000:5e03:8146:c08:57ba:8c50]
In-Reply-To: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
Date: Mon, 22 Oct 2012 16:17:29 -0700
Message-ID: <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Tim Bray <tbray@textuality.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary="e89a8ff253d2a8ff5b04ccae0e31"
X-Gm-Message-State: ALoCoQkRKiK0FA3FTTffbWpNpcqzac78gzRxwup/AzdFidf1GY+Xsf9j6NRwsip/xeKACdKlWprn
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:17:34 -0000
On Mon, Oct 22, 2012 at 3:35 PM, Ian Hickson <ian@hixie.ch> wrote: > > The notion that curl, or an HTTP cache manager, or an XML namespace > > processor, is going to be routing around errors, strikes me on the face > > of it as being wrong. One of the main uses I put curl to is making sure > > I have the URL exactly right before I drop it into chat or whatever. > > $ wget 'http://example.com/a b' > --2012-10-23 00:27:43-- http://example.com/a%20b > > # test.cgi returns a 301 with "Location: a b" > $ curl -L > http://damowmow.com/playground/demos/url/in-http-headers/test.cgi > This file is: > http://damowmow.com/playground/demos/url/in-http-headers/a%20b > > Software does this stuff already. We need to make sure it does it > interoperably. > Hmm. I went to tbray.org and made a file at '$ROOT_DIR/tmp/a b' - note the space. Then I did curl -I 'http://www.tbray.org/tmp/a%20b' curl -I 'http://www.tbray.org/tmp/a b' Curl, quite properly, doesn’t fuck with what I ask it, and revealed a very interesting fact: That my Apache httpd returns 200 for both of these, but, with, uh, interesting variations, amounting to what I think is quite possibly a bug. I also pasted the version with the space into the nearest Web browser, and it quite properly auto-corrected to a%20b. I think it’s a bug that curl is claiming the 301 pointed at "a%20b" not "a b". Because suppose it had pointed at "a%20b" - I don’t want middleware lying to me. It seems like a good idea to document the steps by which "a b" pasted in becomes "a%20b" in the address bar. But I don’t see the relevance outside human-authored strings. -T > > > On Tue, 23 Oct 2012, Julian Reschke wrote: > > > > This always was about venue, not people. If people want to "fix" or > > "augment" URIs/IRIs, they should come over to the IETF. > > I think the person doing the work has the prerogative to do it wherever he > or she wants to do it. Maybe the IETF should consider why Anne isn't doing > it in the IETF. > > > > > The specs don't define everything that implementations have to do to > > > be interoperable. If the IETF doesn't think that's a problem, then > > > that's fine, but then y'all shouldn't be surprised when people who > > > _do_ think that's a problem try and fix it. > > > > Yes, please fix *that*, but *just* that without messing with the basics > > without consensus/review. > > Consensus isn't a value I hold highly, but review of Anne's work is > welcome. > > If the IETF community didn't want Anne to do this work, then the IETF > community should have done it. Having not done it, having not even > understood that the problem exists, means the IETF has lost the > credibility it needs to claim that this is in the IETF's domain. > > You don't get to claim authority over an area while at the same time > telling someone else "please fix that" for the hard work that comes with > that area. The reality is, he who does the hard work, gets the authority. > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' >
- Re: [whatwg] New URL Standard from Anne van Keste… Julian Reschke
- Re: [whatwg] New URL Standard from Anne van Keste… Peter Saint-Andre
- Re: [whatwg] New URL Standard from Anne van Keste… SM
- Re: [whatwg] New URL Standard from Anne van Keste… Brian E Carpenter
- Re: [whatwg] New URL Standard from Anne van Keste… John C Klensin
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Noah Mendelsohn
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Brian E Carpenter
- Re: [whatwg] New URL Standard from Anne van Keste… Julian Reschke
- Re: [whatwg] New URL Standard from Anne van Keste… Tim Bray
- Re: [whatwg] New URL Standard from Anne van Keste… Julian Reschke
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Tim Bray
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Tim Bray
- Re: [whatwg] New URL Standard from Anne van Keste… Julian Reschke
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Noah Mendelsohn
- Re: [whatwg] New URL Standard from Anne van Keste… Roy T. Fielding
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Jan Algermissen
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… James M Snell
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Mark Nottingham
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… mike amundsen
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Graham Klyne
- Re: [whatwg] New URL Standard from Anne van Keste… John Cowan
- websockets in the IETF, was: [whatwg] New URL Sta… Julian Reschke
- Re: [whatwg] New URL Standard from Anne van Keste… Ted Hardie
- Re: [whatwg] New URL Standard from Anne van Keste… Ted Hardie
- Re: [whatwg] New URL Standard from Anne van Keste… Ted Hardie
- Re: [whatwg] New URL Standard from Anne van Keste… Jari Arkko
- Re: [whatwg] New URL Standard from Anne van Keste… Brian E Carpenter
- Re: [whatwg] New URL Standard from Anne van Keste… Stephen Farrell
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: websockets in the IETF, was: [whatwg] New URL… Ian Hickson
- Re: websockets in the IETF, was: [whatwg] New URL… James M Snell
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: websockets in the IETF, was: [whatwg] New URL… Peter Saint-Andre
- Re: [whatwg] New URL Standard from Anne van Keste… Jan Algermissen
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Jan Algermissen
- Re: [whatwg] New URL Standard from Anne van Keste… Christophe Lauret
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- RE: [whatwg] New URL Standard from Anne van Keste… Manger, James H
- Re: [whatwg] New URL Standard from Anne van Keste… David Sheets
- Re: [whatwg] New URL Standard from Anne van Keste… John Cowan
- Re: [whatwg] New URL Standard from Anne van Keste… David Sheets
- RE: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- RE: [whatwg] New URL Standard from Anne van Keste… Manger, James H
- Re: [whatwg] New URL Standard from Anne van Keste… Anne van Kesteren
- Re: [whatwg] New URL Standard from Anne van Keste… Jan Algermissen
- Re: [whatwg] New URL Standard from Anne van Keste… John C Klensin
- Re: [whatwg] New URL Standard from Anne van Keste… Carsten Bormann
- Re: [whatwg] New URL Standard from Anne van Keste… Melinda Shore
- Re: [whatwg] New URL Standard from Anne van Keste… Ian Hickson
- Re: [whatwg] New URL Standard from Anne van Keste… Roy T. Fielding
- Re: [whatwg] New URL Standard from Anne van Keste… David Morris
- Re: [whatwg] New URL Standard from Anne van Keste… David Sheets
- Re: [whatwg] New URL Standard from Anne van Keste… Anne van Kesteren
- Re: [whatwg] New URL Standard from Anne van Keste… Roberto Peon