You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC suggests that relative-path reference should be preceded with a
dot-segment(./) if its 1st segment contains a colon - this is visualized below
with SOLUTION B pseudo code.
Main advantage I see is that adding a dot-segment
is neutral and not visible after reference is resolved.
Additionally, with B, user still has the possibility of expressing : with and without
percent encoding used in 1st segment.
Describe the bug
uri_string:recompose does not handle path-noscheme case (
relative-path reference
in RFC) properly (at least not according to RFC3986)To Reproduce
Expected behavior
1st segment of a path-noscheme should be segment-nz-nc, meaning ':' is not allowed in it and should be percent-encoded
The text was updated successfully, but these errors were encountered: