[spec] IRIs, IDNs, and all that international jazz

[cage]

On Fri, Dec 25, 2020 at 05:57:56PM +0100, Stephane Bortzmeyer wrote:

Hi!

> On Wed, Dec 23, 2020 at 09:26:24PM +0100,
>  cage <cage-dev at twistfold.it> wrote
>  a message of 17 lines which said:
>
> > > The individual path segments actually.
> > >
> > > So, given /Foo/Bar/Baz, decompose the path into individual
> > > segments Foo, Bar, and Baz, encode these, and reconstruct the
> > > path. Easy-peasy.
>
> I don't think that percent-encoding has to be done per path segment. I
> don't find anything in RFC 3986 that makes your algorithm
> mandatory. "/" is a safe character, anyway so it seems to me that you
> can percent-encode the entire path in one operation.

Please correct me  if i am wrong  so this means that if given a path like:

"/è/à/c"

it is safe to send to the server

"%2F%C3%A8%2F%C3%A0%2Fc"

instead of

"/%C3%A8/%C3%A0/c"

I can see that percent-decoding both  the two string above returns the
same results:  the first  path. Could  this be  the reason  because no
splitting is needed?

Bye!
C.