Re: [apps-discuss] Fun with URLs and regex

Julian Reschke <julian.reschke@gmx.de> Wed, 28 January 2015 21:56 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45EE21A039B for <apps-discuss@ietfa.amsl.com>; Wed, 28 Jan 2015 13:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fM2ysyZCyEha for <apps-discuss@ietfa.amsl.com>; Wed, 28 Jan 2015 13:56:25 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C2421A0398 for <apps-discuss@ietf.org>; Wed, 28 Jan 2015 13:56:25 -0800 (PST)
Received: from [192.168.2.175] ([93.217.85.143]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LrvBu-1XY8bT2INa-013gBY; Wed, 28 Jan 2015 22:56:13 +0100
Message-ID: <54C95AF7.6030703@gmx.de>
Date: Wed, 28 Jan 2015 22:56:07 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
References: <C5B10293-E6F6-4348-9782-C9C00A4476CE@mnot.net> <CACweHNBVOrVMesB7HOjPNHe5FtzL1k9XDGAHUXAx5DbOSYv5jA@mail.gmail.com> <A1E5B0EC-FAD5-4178-8C7B-540BEB61DC06@mnot.net> <54AEB660.1020701@intertwingly.net> <F122ADA8-4A96-4F88-BB9F-3C5C6A544067@mnot.net> <54C84872.5040902@intertwingly.net> <EF1E36FA-6A30-4A65-9520-5A31571EE445@mnot.net> <54C95132.2060402@gmx.de> <154ABFBB-AB8C-447A-89A3-D1746EFBF1C6@gbiv.com>
In-Reply-To: <154ABFBB-AB8C-447A-89A3-D1746EFBF1C6@gbiv.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:NofQFp2asuFJnIelDLRbNtmXNDfbcUuu/L9+YKlo5c3lDTvD5FH BLoXbz+bX1AY7MfHL2gLx28TixCPB/ACyV8XU/qvdgfp2L1P7I46D4HAEmaTv4aE32T/TpZ 0AacWbUGLKFnrEwamusedGYxb1QbbKYjJLOr2/92HbTE0DmFWN+DK15QuxMVKcB3IeJcDRb /EXh/qp4hgrHBL5T2TSvg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/nTRiAPGxdNd5BfKV426QuNtdxCk>
Cc: Mark Nottingham <mnot@mnot.net>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Fun with URLs and regex
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 28 Jan 2015 21:56:27 -0000

On 2015-01-28 22:40, Roy T. Fielding wrote:
> On Jan 28, 2015, at 1:14 PM, Julian Reschke wrote:
>> On 2015-01-28 06:36, Mark Nottingham wrote:
>>> ... which brings about another interesting observation -- only http and https define fragments in their syntax; the other schemes do not.
>>> ...
>>
>> It's because you asked for that in <https://lists.w3.org/Archives/Public/ietf-http-wg/2013AprJun/0187.html>, and apparently were successful in convincing Roy.
>
> It is a very very very old debate regarding whether the fragment is part
> of a URI or something attached to the end of a URI, but that was resolved
> in RFC3986 (since the only thing that really matters here is that a fragment
> is going to be parsed as such regardless of the scheme).
>
> HTTP was merely updated to reflect what STD66 calls a URI.

I agree that the fragment is part of the URI; the question, as far as I 
understand, is whether the *scheme* definition should include the 
fragment, given the fact that you can attach a fragment to any URI anyway.

Best regards, Julian