ed2bac026d
Until this PR, we were naively closing the quic.Stream whenever the callstack for handling the request (HTTP or TCP) finished. However, our proxy handler may still be reading or writing from the quic.Stream at that point, because we return the callstack if either side finishes, but not necessarily both. This is a problem for quic-go library because quic.Stream#Close cannot be called concurrently with quic.Stream#Write Furthermore, we also noticed that quic.Stream#Close does nothing to do receiving stream (since, underneath, quic.Stream has 2 streams, 1 for each direction), thus leaking memory, as explained in: https://github.com/lucas-clemente/quic-go/issues/3322 This PR addresses both problems by wrapping the quic.Stream that is passed down to the proxying logic and handle all these concerns. |
||
|---|---|---|
| .. | ||
| schema | ||
| conversion.go | ||
| datagram.go | ||
| datagram_test.go | ||
| metrics.go | ||
| param_unix.go | ||
| param_windows.go | ||
| pogs.go | ||
| quic_protocol.go | ||
| quic_protocol_test.go | ||
| safe_stream.go | ||
| safe_stream_test.go | ||
| test_utils.go | ||
| tracing.go | ||