From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Vivien Kraus Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH v4] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2. Date: Fri, 03 Nov 2023 19:19:40 +0100 Message-ID: <29bc7dabd0a452646fccbf0feaf9a79fef9eb3db.camel@planete-kraus.eu> References: <87fs1n53de.fsf@nborghese.com> <92c8a960b091300107e523126887fd1c246a0fda.camel@planete-kraus.eu> <87o7ga905j.fsf@nborghese.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27196"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.46.4 Cc: guile-devel@gnu.org To: Nathan Original-X-From: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Fri Nov 03 19:20:13 2023 Return-path: Envelope-to: guile-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qyymC-0006qW-LK for guile-devel@m.gmane-mx.org; Fri, 03 Nov 2023 19:20:12 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qyylu-0000MC-NO; Fri, 03 Nov 2023 14:19:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qyyls-0000Lu-Cm for guile-devel@gnu.org; Fri, 03 Nov 2023 14:19:52 -0400 Original-Received: from planete-kraus.eu ([89.234.140.182]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1qyylm-0004rl-Pv for guile-devel@gnu.org; Fri, 03 Nov 2023 14:19:52 -0400 Original-Received: from planete-kraus.eu (localhost.lan [127.0.0.1]) by planete-kraus.eu (OpenSMTPD) with ESMTP id b8b65d73; Fri, 3 Nov 2023 18:19:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=planete-kraus.eu; h= message-id:subject:from:to:cc:date:in-reply-to:references :content-type:content-transfer-encoding:mime-version; s= albinoniA; bh=jISz9XlKR+b9VAtKN2tfNKqPodE=; b=HoB/vssSy/0gemXhba HgxOTje2ZvF/h9PNK/D4iEYYQ28kCK8z9avxZHr7tSSzOByRih3Svxf90UaMZ90k mJRxmkcnSHcCvEqF6jBIGxPGuaUCvbeL40PFCoyid5hGUSpmGpmzZHkM94bXR2yL RBT26zOeTKiqqbVlQkU+BIhPlk8xP3FEZtVTi0Cg8baBdefso4/1A58xu7W73Zqt XPe4GhHQRvdBZBogldNwJACi4H6xEL9zVMSM6xkUP0mcYm1d9avjkHj6q3nxYRKu T6nKbONkmEQpczGOJyAnmZap7REMoTD8/jgIL+eBDyDL/QTpB1C7j6ANAGy3hq3U raww== Original-Received: by planete-kraus.eu (OpenSMTPD) with ESMTPSA id d7a18a1b (TLSv1.3:TLS_CHACHA20_POLY1305_SHA256:256:NO); Fri, 3 Nov 2023 18:19:42 +0000 (UTC) In-Reply-To: <87o7ga905j.fsf@nborghese.com> Received-SPF: pass client-ip=89.234.140.182; envelope-from=vivien@planete-kraus.eu; helo=planete-kraus.eu X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.lisp.guile.devel:22062 Archived-At: Le vendredi 03 novembre 2023 =C3=A0 13:49 -0400, Nathan a =C3=A9crit=C2=A0: > > This pushes the limits of my understanding of URIs, as I did not > > know > > we had to consider '%2E%2E' the same as '..'. However, the RFC is > > not > > very clear: >=20 > I wasn't able to find anything that MANDATED any normalization at > all, either before or after Relative Resolution. It is possible that > treating %2E as a literal dot in resolve-relative-reference could > count as unwanted normalization. But it's a safe operation in terms > of URI equivalence* and I think users would be less confused to have > %2E%2E disappear than to have it remain. >=20 > Also, what if the resolve-relative-reference procedure didn't treat > %2E as a dot? > There isn't a uri-normalize procedure users can call afterwards to > fix that. > And there isn't a version of uri-decode that allows selectively > decoding JUST the dot characters. > Users would have to write a lot of code themselves to get proper > relative-resolution, so we should do it for them. First of all, I just noticed I spelled your name wrong, sorry. I=E2=80=99m convinced the decision you made to consider '.' and '%2E' equivalent is the correct one, if that was not clear for everyone. Best regards, Vivien