Re: URL, URI and the w3c
Daniel Stenberg <daniel@haxx.se> Tue, 14 June 2022 10:28 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9F0C1655D7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jun 2022 03:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.66
X-Spam-Level:
X-Spam-Status: No, score=-2.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucQiyhstBAOI for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jun 2022 03:28:20 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D4D2C1649FF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 Jun 2022 03:28:10 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1o13jf-0008CJ-A2 for ietf-http-wg-dist@listhub.w3.org; Tue, 14 Jun 2022 10:25:23 +0000
Resent-Date: Tue, 14 Jun 2022 10:25:23 +0000
Resent-Message-Id: <E1o13jf-0008CJ-A2@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <daniel@haxx.se>) id 1o13je-0008BL-5i for ietf-http-wg@listhub.w3.org; Tue, 14 Jun 2022 10:25:22 +0000
Received: from silly.haxx.se ([159.253.31.95]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <daniel@haxx.se>) id 1o13jY-0004XM-Rl for ietf-http-wg@w3.org; Tue, 14 Jun 2022 10:25:22 +0000
Received: by silly.haxx.se (Postfix, from userid 1001) id 016AE62158; Tue, 14 Jun 2022 12:25:04 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by silly.haxx.se (Postfix) with ESMTP id F3E1E7D59D; Tue, 14 Jun 2022 12:25:03 +0200 (CEST)
Date: Tue, 14 Jun 2022 12:25:03 +0200
From: Daniel Stenberg <daniel@haxx.se>
To: Roberto Polli <robipolli@gmail.com>
cc: HTTP Working Group <ietf-http-wg@w3.org>, Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>
In-Reply-To: <CAP9qbHVQ7B423jc7tHQo70ZAeXmFHdZo-=JvTSj5L2D6uTTQ9A@mail.gmail.com>
Message-ID: <3n57428s-3052-66q7-prp8-118s19q41461@unkk.fr>
References: <CAP9qbHVQ7B423jc7tHQo70ZAeXmFHdZo-=JvTSj5L2D6uTTQ9A@mail.gmail.com>
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Received-SPF: pass client-ip=159.253.31.95; envelope-from=daniel@haxx.se; helo=silly.haxx.se
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1o13jY-0004XM-Rl 0838d1c467067b3a58e79ee99de3bb36
X-Original-To: ietf-http-wg@w3.org
Subject: Re: URL, URI and the w3c
Archived-At: <https://www.w3.org/mid/3n57428s-3052-66q7-prp8-118s19q41461@unkk.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40098
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On Tue, 14 Jun 2022, Roberto Polli wrote: > I noted that some specs reference URL/URI from https://url.spec.whatwg.org/ > while others use https://www.rfc-editor.org/rfc/rfc3986 & co. > I assume that those specs are aligned, isn't it? They are very much not aligned. There are plenty of ways we can write URLs and URIs that parse differently based on these specs. I collect some of those issues here: https://github.com/bagder/docs/blob/master/URL-interop.md -- / daniel.haxx.se
- URL, URI and the w3c Roberto Polli
- Re: URL, URI and the w3c Daniel Stenberg
- Re: URL, URI and the w3c Carsten Bormann
- Re: URL, URI and the w3c Roberto Polli
- Re: URL, URI and the w3c Julian Reschke
- Re: URL, URI and the w3c Tim Bray
- Re: URL, URI and the w3c Justin Richer
- Re: URL, URI and the w3c Daniel Stenberg
- Re: URL, URI and the w3c Daniel Stenberg
- Re: URL, URI and the w3c Tim Bray
- Re: URL, URI and the w3c Stefan Eissing
- Re: URL, URI and the w3c Eric J Bowman
- Re: URL, URI and the w3c Roy T. Fielding