Tags: MetaCubeX/quic-go
Tags
metrics: add an example Grafana dashboard (quic-go#4559) * metrics: add an example Grafana dashboard * metrics: rename Handshake Duration to Handshake Latency Co-authored-by: sukun <[email protected]> --------- Co-authored-by: sukun <[email protected]>
http3: fix memory leak in stream state tracking (quic-go#4523) * fix(http3): handle streamStateSendAndReceiveClosed in onStreamStateChange Signed-off-by: George MacRorie <[email protected]> * refactor(http3): adjust stateTrackingStream to operate over streamClearer and errorSetter * test(http3): remove duplicate test case * chore(http3): rename test spies to be mocks --------- Signed-off-by: George MacRorie <[email protected]>
http3: pass original Conn to ConnContext (quic-go#4480) * http3: Pass original Conn to ConnContext quic-go#4479 * Update test to check conn value
http3: sniff Content-Type when flushing the ResponseWriter (quic-go#4412 ) * try to sniff content-type as long as the data is not written to the client * only write when body is allowed * fix tests * fix tests * fix header count * fix lint * merge from upstream * merge updates from master * Update http3/response_writer.go Co-authored-by: Marten Seemann <[email protected]> --------- Co-authored-by: Marten Seemann <[email protected]>
close connection when an abnormally large number of frames are queued (… …quic-go#4369) Under normal circumstances, we should be able to send out control frames right away, so we don't expect any queue to build up. To defend against resource exhaustion attacks, we limit the control frame queue to 16384 elements.
http3: automatically add content-length for small responses (quic-go#… …3989) * response writer: add content-length automatically when response is small enough and doesn't call Flush * fix comment * add integration test * Update http3/response_writer.go * Update integrationtests/self/http_test.go --------- Co-authored-by: Marten Seemann <[email protected]>
PreviousNext