-
Example:
The expected issuer is `https://example.com`, but the well-known/openid-configuration reports `https://example.com/` with a trailing slash.
Currently, this leads to the Err(ProviderMetadata…
-
Today, when a user passes in a cloud URI, we "consume" the parameters that we know how to process depending on the cloud provider. We do not normalize the parameters passed in by the user and so unles…
-
When a query parameter includes `%26`, `normalized_encode` replaces it with a literal `&`, which results in a different URI:
```ruby
pry(main)> Addressable::URI.normalized_encode("https://example.co…
-
As noted in #606 and elsewhere, the URL APIs strongly lean towards preserving input in path and query components, and therefore differentiating URIs that are equivalent per e.g. https://www.rfc-editor…
-
Checklist:
* [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
* [x] I've included steps to reproduce the bug.
* [x] I've pasted the output of `argocd version`.
*…
-
non-normalized URIs will be normalized after `popstate`, which breaks cache storage.
eg. /player/乔丹/
-
(uri/normalize-path "http://foo.bar/../../../")
=> "http://foo.bar../../"
I am not 100% sure but I think that the normalized version of this uri should stay the same as the origin.
-
I have a redirect that is based on the context path of the request. The context path is not user entered and will be set to whatever the context is being used.
In addition, the URI being assembled w…
-
There are a few places where the implementation of the Uri class and its parser Rfc3986Parser deviate from the [RFC 3986 specification](https://www.ietf.org/rfc/rfc3986.txt)
1. Currently, the class Ur…
-
`lambdaisland.uri/uri-str` does not URL-encode username and password:
```clj
(->URI "http" "fan:cy" "s@cr3d!" "example.com" nil nil nil nil)
;=> #lambdaisland/uri"http://fan:cy:s@cr3d!@example.com"…