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
Clink “corrupts” URL if the query part contains a character from the unwise set of characters. By corrupts, I mean percent encodes characters like “[“ or “]”. This is fine if you live in a world where all URLs obey https://url.spec.whatwg.org/, but I see URLs like https://foo.foo/?param[]=1¶m[]=2 in the wild.
The problem is if you have clink in the background and copied URL like that you will get https://foo.foo/?param%5B%5D=1¶m%5B%5D=2 which is a bug from the user point of view.
Why?
Clink internally uses url crate for URL manipulation. It percent encodes keys and values when you append pair to a query without the possibility to opt out.
Description:
Clink “corrupts” URL if the query part contains a character from the unwise set of characters. By corrupts, I mean percent encodes characters like “[“ or “]”. This is fine if you live in a world where all URLs obey https://url.spec.whatwg.org/, but I see URLs like https://foo.foo/?param[]=1¶m[]=2 in the wild.
The problem is if you have clink in the background and copied URL like that you will get https://foo.foo/?param%5B%5D=1¶m%5B%5D=2 which is a bug from the user point of view.
Why?
Clink internally uses url crate for URL manipulation. It percent encodes keys and values when you append pair to a query without the possibility to opt out.
What to do?
The text was updated successfully, but these errors were encountered: