-
URI Normalization is needed for consistency when comparing URIs.
RFC3986 gives some guidelines, but it is hardly enough, as we already noticed with the http vs https debate that we had because of b…
-
The common case of setting URI on lsp4j message object is `URI#toString()` call. For example LSP4E sets uri on the `TextDocumentIdentifier` via `URI#toString()` call rather than `URI#toASCIIString()`.…
-
Right now we treat hash URIs as strings. The hash algorithm does its own logic to generate a list of arbitrary paths and we use them as-is.
I think what we should do is redefine the hash algorithms t…
-
### Code
```Rust
```
### Meta
`rustc --version --verbose`:
```
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
h…
-
`Request#perform` internally normalizes the URI. So HTTP request may not be sent to the actual URL. For example, if the URI is `https://en.wiktionary.org/wiki/①`, a request will be sent to `https://en…
-
As far as I see, `fluent_uri==0.3.0` normalizes `http://example.com` and `http://example.com:80` to different values and therefore does not consider them equal. My reading of [RFC 3986 6.2.3](https://…
-
**API Platform version(s) affected**: 3.3.11
**Description**
I have a custom `Symfony\Component\Serializer\Normalizer\DenormalizerInterface` class, which converts the request context to a typed (…
-
Looking at the http://www.faqs.org/rfcs/rfc2396.html I don't see anything there about automatic normalization (prohibiting storing URIs as not normalized). In the section about normalization (`6. URI …
-
https://en.wikipedia.org/wiki/URI_normalization
Normalizations that preserve semantics
The following normalizations are described in RFC 3986 [1] to result in equivalent URIs:
Converting percent-…
-
It ought to be possible for the user-agent to express a preference or requirement for one of two resulting URI behaviors:
- URI that encodes the request body
- URI that does _not_ encode the req…