Marten Seemann

Oops, you’re right.

Fix in https://github.com/quic-go/quic-go/pull/4666. Would appreciate a quick code review 🙏

Am I right to assume that this is due to this line? https://github.com/quic-go/quic-go/blob/c9ae1529568347d445240e0d2449cce4b73a8602/http3/roundtrip.go#L270-L272 How does `net/http` get around the bug that you linked?

Very interesting. I've played around with the h3dial a bit, thank you for providing such a great example code! Using `net.DialUDP` doesn't work, as it requires a `net.UDPAddr`, and we'd...

@quaintdev You can set the `Dial` callback on the `http3.Transport`, and dial a QUIC connection on UDP6 there. Does that work for you?

Please refer to https://quic-go.net/docs/webtransport/. We have sample code for both client and server side there.

We could add some example code to this repo though, similar to what we have in quic-go.

You can detect simultaneous open in the security protocol, for example when a TLS client receives a TLS ClientHello. crypto/tls emits a really specific error. Then you can do a...

No, there's no way to do that, see https://github.com/libp2p/go-libp2p/issues/1432.

I'm not really sure how your setup looks like, but if a request don't have a Content-Length, you'll need to read until the end of the stream. Are you saying...