reqwest crashes with the following panic when given URLs containing the caret character:
thread 'reqwest-internal-sync-runtime' panicked at 'a parsed Url should always be a valid Uri: InvalidUri(InvalidUriChar)', libcore/result.rs:1009:5
Does this mean that clients of the crate should always check for unsafe characters before passing them to the library to avoid such panics?
No, I believe such a panic is an actual bug in reqwest. I'll look into it.
This was fixed in http v0.1.16. Running cargo update -p http should fix anyone experiencing this.
Got this today trying to install rust behind a proxy, is rustup-init using the right version ?
@mmacedoeu looks like not, its lockfile sets http 0.1.13, before the fix.