HTTP v3 support

[xbyte83]

Any chance to add v3 support?

[vlourme]

I'm a bit curious if HTTP3 is really beneficial here. I've not seen any clients doing proxy requests using HTTP/3. Also when doing HTTPS (CONNECT), it forwards bytes so HTTP/2 (likely not HTTP/3 because UDP-based) is working.

Do you have example of any clients that do proxy over HTTP/3?

[xbyte83]

Currently, our client always negotiates HTTP/2, but many major sites are already rolling out HTTP/3. For example, try loading google.com in a regular browser versus through a proxy—and inspect all the request frames. You’ll see that HTTP/3 behaves differently.

Soon, sites may outright block HTTP/2 traffic, since it makes proxy and bot detection trivial. If you’re only making simple curl calls, it might not matter much—but for a full-featured proxy, HTTP/3 support is becoming essential.

Fortunately, adding HTTP/3 is straightforward with quic-go and its HTTP/3 package:

github.com/quic-go/quic-go

github.com/quic-go/quic-go/http3

That said, this is exactly where sticky sessions become crucial for maintaining connection affinity.

By the way, when I looked at your source, it seemed you’re not using net/http for your transport layer—can you confirm whether that’s intentional?

Feel free to reach out if you’d like to discuss this in more detail. I’m available 24/7!

[vlourme]

Good point, I totally understand.

You're right, actually raw TCP and rewritten HTTP parser is used. The idea behind this was:

• Raw TCP:
  • Allow easier copy between connection without doing HTTP Hijack
  • Can allow SOCKS4/5 later by checking the "magic byte" and then process HTTP and SOCKS differently on the same port and listener
• Rewritten HTTP parser:
  • It's a very simplified HTTP parser that only parse request line and headers without body, which makes it much faster than standard lib parser and allocate less

I'll dive into quic-go and see what is possible, I guess it's quite different due to UDP.

---

Also, for the record, my goal with this project is to make the fastest HTTP forwarding proxy possible. I did many tests in Rust, Zig and Go. I ended up making it in Go for simplicity but I'm still doing a lot of trials in Zig and soon C as I'm beginning some experimentations with DPDK and AF_XDP stack. But I totally agree that making it HTTP/3 compliant can be a very good point for bot detection as most browsers use HTTP/2 or HTTP/3 today. (which is not the case of mobile apps that still often use HTTP/1.1 for API calls).

Edit: Should we go for this? https://quic-go.net/docs/connect-udp/proxy/#handling-proxying-requests
This seems very different from usual HTTP/1.1 proxy which is based on headers, it's based on URL here?

Edit 2: socks5 can be wrapped into quic? https://github.com/number571/go-http3-proxy/blob/8bb0b3cb801ee456a50249ea23ecc41fa198be3e/cmd/client/main.go#L79