Open FraMecca opened 5 years ago
Thanks for the report! This is a somewhat awkward problem to work around.
%E4f
is not a valid UTF-8 sequence, so percent-decoding it would result in an invalid string that would blow up later.
Right now, urld auto-encodes query parameters, so not decoding that sequence would fail to round-trip correctly — it would turn into '%25E4'.
What urld needs to do is keep around both the encoded and unencoded version of each string.
Why do you need to store query parameters as encoded sequence?
The url in question is: https://www.blogfree.net/?l=4&wiki=Allgemeine_Gesch%E4ftsbedingungen"