Den Delimarsky

Thanks for the report @cbjfan2009 - I will investigate this issue.

@mairaw yes, I updated the title, thanks for the heads-up!

Hi folks, we've assessed this feature request and have determined that **we will not be able to address it at this time**. Our documentation is generated entirely from binaries (shipped...

@philippjbauer I'll chime in as an uninvested third-party, since I no longer work at the company, but the only way to do this is to download the documentation locally and...

Heya folks @mre @vipulgupta2048 - any luck with the changes? Looks like the panic is still a thing (and [the PR](https://github.com/seanmonstar/reqwest/pull/1399) is taking some time to be reviewed). Is there...

ACK - thank you so much, @mre and @lebensterben. There are hundreds of URLs that panic for me (mostly ones from Archive.org that are of the form `https://web.archive.org/some_stub/https://my_archived_url`), so I'll...

@mre here is an example that I saw pop up today: ```bash thread 'tokio-runtime-worker' panicked at 'a parsed Url should always be a valid Uri: InvalidUri(InvalidUriChar)', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.11.8/src/into_url.rs:70:14 note: run with...

> I don't understand why the URLs are invalid. Absolutely the same - they are resolving properly and work with no issue in the browser.

Here's an example of how this is panicking with an Archive.org URL today: ```bash thread 'tokio-runtime-worker' panicked at 'a parsed Url should always be a valid Uri: InvalidUri(InvalidUriChar)', /cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.11.8/src/into_url.rs:70:14 note:...

BTW, it's entirely possible that my GitHub action is just not configured properly because I am trying to exclude a folder from being checked: ```yml - name: Load Excludes run:...