QUIC：After sending a RESET_STREAM, nginx does not cease transmission of STREAM frames?
|Reported by:||Owned by:|
|uname -a:||Linux dev.na61 4.19.91-008.x86_64 #1 SMP Fri Sep 4 17:33:26 CST 2020 x86_64 x86_64 x86_64 GNU/Linux|
nginx version: nginx/1.25.2
built by gcc 9.3.0 (GCC)
built with OpenSSL 1.1.0 (compatible; BoringSSL) (running with BoringSSL)
TLS SNI support enabled
configure arguments: --with-debug --with-http_v3_module --prefix=/home/yefei.dyf/nginx --with-cc-opt=-I/home/yefei.dyf/boringssl/include --with-ld-opt='-L/home/yefei.dyf/boringssl/ssl -L/home/yefei.dyf/boringssl/crypto'
RFC 9000, 19.4 has a related statement about RESET_STREAM frame.
After sending a RESET_STREAM, an endpoint ceases transmission and retransmission of STREAM frames on the identified stream. A receiver of RESET_STREAM can discard any data that it already received on that stream.
I found the logic to cease the retransmission of STREAM frames in
qs->send_state was NGX_QUIC_STREAM_SEND_RESET_SENT or NGX_QUIC_STREAM_SEND_RESET_RECVD.
When sending a stream frame, was also to cease transmission of STREAM frames in