On 2021/11/06 17:29, Klemens Nanni wrote: > Encoding URL paths changes the requested URL and therefore may yield > different responses (opposed to an unencoded URL), solely depending on > how the server implements de/encoding.
Makes sense as this matches what various other tools that fetch URLs do for printing. Or another approach would be to not output the URL at all (it's still visible with -d).
