How should %2F in resource URLs be interpreted?

[RubenVerborgh]

No description provided.

[ThisIsMissEm]

This may be relevant: https://simonwillison.net/2022/Mar/5/dash-encoding/

[kjetilk]

I see you reference RFC 3986 there in a discussion around URI equivalence, but I think the relevant section is 2.1:

A percent-encoding mechanism is used to represent a data octet in a component when that octet's corresponding character [...] is being used as a delimiter of, or within, the component.

In this case, "/" is delimiter, as per the same RFC, and so the percent encoded character is a data octet, that is, "any other character". The URI normalization is also given there.

I'm not sure we should put this in the protocol spec, but we should write a test case for it in a future "relevant tests outside of the protocol spec" test suite to ensure that it does not influence the containment hierarchy in any way. Indeed, foo/bar and foo%2Fbar are two different resources.

[kjetilk]

I created a label to use for things that needs to be revisited for tests, and with that, I think it is OK to close this. Feel free to reopen if you don't agree.