Open FiV0 opened 2 years ago
Normalize does not currently handle dot segments or default ports, it only deals with percent encoding at the moment. We do have the algorithm for dot segment resolution implemented as part or uri/join
, I think it could make sense to add that to normalize.
(norm/normalize (uri/uri "http://foobar.com/api/some%2Fdata")) (norm/normalize (uri/uri "http://foobar.com/api/some/data"))
This is indeed a bug. We handle special delimteres in the query segment, but not in the path segment. A PR for that is welcome as well.
I will try to have a look when I find the time.
This issue includes a bug so it makes sense to keep open.
From the naming I gathered that the intended use case for
normalize
was that uris that are semantically equivalent should get a canonical form. Some examples where this is currently not the case:Path segments:
Scheme based normalization (the following are urls are equivalent)
See here.
Is this sort of out of scope for this library? Should this be added?
Also, from my understanding of rfc3986, but this might be wrong, if I want to use a reserved character as part of the data I need to percent-encode it. For example, let's say I want to use
/
in my data, the request for an endpoint of/api/{data}
could look for example something like"http://foobar.com/api/some%2Fdata"
.normalize
would then confound the following two uris.So my question is, shouldn't only unreserved characters be decoded as part of the normalization?