Marten Seemann

Is this the same issue as https://github.com/libp2p/go-libp2p/issues/1930?

I was unable to reproduce this failure. Here's what I did: ```sh ssh-keygen -f mykey # creates mykey and mykey.pub ssh-keygen -s mykey -I 1234 mykey.pub # creates mykey-cert.pub ln...

Yes that's correct! There were no API changes for graceful shutdown, so as long as you're calling `Shutdown`, everything should work as expected. On the server side, instead of just...

Huh, this is weird. What's going on here? Compiling ns3 from scratch takes more than an hour, see https://github.com/quic-interop/quic-network-simulator/actions/runs/7465935034/job/20328138279?pr=124

@inetol Could you record a qlog of the transfer and post it here? As of https://github.com/caddyserver/caddy/pull/6581, this is possible to setting the QLOGDIR env.

The qlog looks fine, the client doesn't even send an error. I'm not sure what NS_ERROR_CORRUPTED_CONTENT means in the first place, so it's hard to speculate what could cause this....

Thank you for bisecting @inetol! So it looks like this is actually a `Content-Length` issue. Would you mind re-running your test on this branch? https://github.com/quic-go/quic-go/compare/print-http3-headers All I did was add...

No idea what’s going on then. If we’re not sending any headers, how can they cause any problems?

@inetol Where did the request body change in https://github.com/quic-go/quic-go/commit/7c3544ca34bc4ea1dc6e37381f7b395bc9936aa5? I just tested quic-go v0.47.0 with a HEAD request, and it has a `Body` set on both the `http.Request` (on the...

Is there any discrepancy between HTTP/3 and the standard library HTTP versions with regards to the `Content-Length` field, that leads to this error surfacing on HTTP/3, but not on older...