`--insecure` flag does not work with self-signed cert hosted in a Docker container

[tomcodes]

Hi!

Thanks for the great project, Lychee is a delight to use.

I wanted to test some local app that runs in Docker, pretty standard PHP / nginx stack with self signed cert.

When I launch Lychee with the insecure flag I got this error:

lychee --insecure https://super.app.test
Error: Network error

Caused by:
    0: error sending request for url (https://super.app.test/)
    1: client error (Connect)
    2: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2104: (self-signed certificate)
    3: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:2104:

This local app is reachable from my browser (after I allow the self-signed cert in Firefox).

Is there a way to bypass this error?

[mre]

Thanks! According to the docs we already allow accepting invalid certificates:

lychee/lychee-lib/src/client.rs

Lines 343 to 349 in e185e90

	let mut builder = reqwest::ClientBuilder::new()
	.gzip(true)
	.default_headers(headers)
	.danger_accept_invalid_certs(self.allow_insecure)
	.connect_timeout(Duration::from_secs(CONNECT_TIMEOUT))
	.tcp_keepalive(Duration::from_secs(TCP_KEEPALIVE))
	.redirect(redirect_policy);

Maybe there's another setting in reqwest that we miss.