From: Vivien Kraus <vivien@planete-kraus.eu>
To: Nathan <nathan_mail@nborghese.com>
Cc: guile-devel@gnu.org
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 [thread overview]
Message-ID: <29bc7dabd0a452646fccbf0feaf9a79fef9eb3db.camel@planete-kraus.eu> (raw)
In-Reply-To: <87o7ga905j.fsf@nborghese.com>
Le vendredi 03 novembre 2023 à 13:49 -0400, Nathan a écrit :
> > 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:
>
> 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.
>
> 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’m convinced the decision you made to consider '.' and '%2E'
equivalent is the correct one, if that was not clear for everyone.
Best regards,
Vivien
next prev parent reply other threads:[~2023-11-03 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 16:48 [PATCH] Add resolve-relative-reference in (web uri), as in RFC 3986 5.2 Vivien Kraus
2023-09-25 20:46 ` Maxime Devos
2023-09-25 16:48 ` [PATCH v2] " Vivien Kraus
2023-10-02 16:32 ` Vivien Kraus
2023-10-03 18:49 ` Maxime Devos
2023-09-25 16:48 ` [PATCH v3] " Vivien Kraus
2023-10-03 18:56 ` [PATCH v2] " Dale Mellor
2023-10-03 19:04 ` Maxime Devos
2023-10-03 20:03 ` [PATCH] " Vivien Kraus
2023-10-03 22:22 ` Maxime Devos
2023-10-03 22:30 ` Maxime Devos
2023-10-04 5:29 ` Vivien Kraus
2023-10-10 21:44 ` Maxime Devos
2023-09-25 16:48 ` [PATCH v4] " Vivien Kraus
2023-11-02 20:00 ` Nathan via Developers list for Guile, the GNU extensibility library
2023-11-02 20:48 ` Vivien Kraus
2023-11-03 17:49 ` Nathan via Developers list for Guile, the GNU extensibility library
2023-11-03 18:19 ` Vivien Kraus [this message]
2023-11-27 17:10 ` Vivien Kraus
2023-11-27 17:15 ` Vivien Kraus
2023-11-29 1:08 ` Nathan via Developers list for Guile, the GNU extensibility library
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29bc7dabd0a452646fccbf0feaf9a79fef9eb3db.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=guile-devel@gnu.org \
--cc=nathan_mail@nborghese.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).