HTTP/2 + TLS connection between client <-> proxy

[0x192]

Correct me if I'm wrong but there seems to be no built-in support for HTTP/2 over TLS between the client and the proxy:

I tried with the http2 feature from the example:

w1nst0n@host/t/hudsucker> cargo run --example noop --features http2
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.21s
     Running `target/debug/examples/noop`
2025-05-06T15:07:32.962520Z ERROR hudsucker::proxy: Error serving connection: invalid HTTP method parsed
2025-05-06T15:07:38.932202Z ERROR hudsucker::proxy: Error serving connection: invalid HTTP method parsed

w1nst0n@host/t/h/e/ca> curl -4L --proxy-http2 --proxy http://127.0.0.1:3000 --cacert hudsucker.cer https://archlinux.org
curl: (35) Send failure: Broken pipe

```cmd
w1nst0n@host/t/h/e/ca> curl -4L --proxy-http2 --proxy https://127.0.0.1:3000 --cacert hudsucker.cer https://archlinux.org
curl: (35) Send failure: Broken pipe

Thank you for working on this project!

[omjadas]

Thanks for the suggestion. You are correct that this is not currently possible, but it should be relatively easy to implement. I will try to look into this over the next couple of weeks.

[colorfulsing]

@omjadas thanks for taking a look into this. We are using hudsucker on our company as part of a reverse-proxy system and having this feature would be extremely useful.

Thanks in advance! 👍