Hi, this looks super interesting, I'm wondering where in a warp filter chain or routes specification I would call this though, do you have a simple example of using this?

Perhaps bind to SocketAddr::from_str("[::]:80").unwrap() and SocketAddr::from_str("[::]:443").unwrap() instead of 0.0.0.0 ? That way it listens to both IPv4 and IPv6. Or better, allow this to be specified, since listening to the v6 address isn't necessarily dual-stack on not-Linux (in that case, have to bind to both separately).

Thanks for this great library, I was unaware that TLS can be this easy. What kind of license do you have for it?

This crate depends on acme_lib, which on turn depends on openssl.

But warp does not use openssl - it uses rustls. So an app built with lets-encrypt-warp currently ends up depending on two completely different TLS implementations.

Therefore, it would make more sense if this crate used rustls-acme instead.

This crate currently uses warp 0.2, but I am using 0.3. I am getting version conflicts.

    |
216 | /     impl<FN, F> FilterBase for WithLog<FN, F>
217 | |     where
218 | |         FN: Fn(Info) + Clone + Send,
219 | |         F: Filter + Clone + Send,
...   |
234 | |         }
235 | |     }
    | |_____^
= note: perhaps two different versions of crate `warp` are being used?

I will open a PR.