Re: URL, URI and the w3c
Daniel Stenberg <daniel@haxx.se> Tue, 14 June 2022 21:36 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 7BFABC157B54 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jun 2022 14:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level:
X-Spam-Status: No, score=-2.657 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 YpoqU4LVPZOT for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jun 2022 14:36:27 -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 B58C2C157B59 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 Jun 2022 14:36:27 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1o1EAC-00081z-7i for ietf-http-wg-dist@listhub.w3.org; Tue, 14 Jun 2022 21:33:28 +0000
Resent-Date: Tue, 14 Jun 2022 21:33:28 +0000
Resent-Message-Id: <E1o1EAC-00081z-7i@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 1o1EAB-000816-3M for ietf-http-wg@listhub.w3.org; Tue, 14 Jun 2022 21:33:27 +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 1o1EA9-0008KV-Lo for ietf-http-wg@w3.org; Tue, 14 Jun 2022 21:33:26 +0000
Received: by silly.haxx.se (Postfix, from userid 1001) id 6754862022; Tue, 14 Jun 2022 23:33:12 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by silly.haxx.se (Postfix) with ESMTP id 66A4D7D9BA; Tue, 14 Jun 2022 23:33:12 +0200 (CEST)
Date: Tue, 14 Jun 2022 23:33:12 +0200
From: Daniel Stenberg <daniel@haxx.se>
To: Tim Bray <tbray@textuality.com>
cc: Roberto Polli <robipolli@gmail.com>, Carsten Bormann <cabo@tzi.org>, HTTP Working Group <ietf-http-wg@w3.org>, Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>, Ted Hardie <ted.ietf@gmail.com>
In-Reply-To: <CAHBU6iuxgqbkC3nLUi7w+o4JcSMPkW3FmC1b1C4=qRM-ZxUWiQ@mail.gmail.com>
Message-ID: <895n295o-175q-ppn7-1472-p4np728p70o1@unkk.fr>
References: <CAP9qbHVQ7B423jc7tHQo70ZAeXmFHdZo-=JvTSj5L2D6uTTQ9A@mail.gmail.com> <3n57428s-3052-66q7-prp8-118s19q41461@unkk.fr> <A90EB729-EA13-42E1-94F1-4410334E907E@tzi.org> <CAP9qbHUDSGDWyDUzLykFkE_C+GKZGy5SYxNsX=feEnrAmkE1Bw@mail.gmail.com> <CAHBU6iuxgqbkC3nLUi7w+o4JcSMPkW3FmC1b1C4=qRM-ZxUWiQ@mail.gmail.com>
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-39887073-683603103-1655242392=:2218147"
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 1o1EA9-0008KV-Lo 1722763e774d37fa0e4796b999b8e984
X-Original-To: ietf-http-wg@w3.org
Subject: Re: URL, URI and the w3c
Archived-At: <https://www.w3.org/mid/895n295o-175q-ppn7-1472-p4np728p70o1@unkk.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40104
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, Tim Bray wrote: > I think it’s the case that browsers will accept any 3986-conforming URI > that is within its abilities, i.e. http:, https: (and maybe ftp, etc?). No, sorry, that's not true. The browsers accept and work with the WHATWG URL spec style of URLs and they are incompatible with 3986-conforming URIs (and 3987 IRIs) in numerous ways. As I've explained. -- / 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