Closed chrisgrieser closed 5 days ago
Fixed in v1.14.0 - url should no longer be encoded
Testing this with v1.14.0, by default the URL is not encoded, but for some reason passing either --encode-urls
or --no-encode-urls
produces encoded URL.
can confirm, passing nothing keeps the URL unencoded, while --no-encode-urls
results in the URL being encoded, basically the original problem.