diff options
| author | Vladimir Homutov <vl@nginx.com> | 2020-05-22 18:14:35 +0300 |
|---|---|---|
| committer | Vladimir Homutov <vl@nginx.com> | 2020-05-22 18:14:35 +0300 |
| commit | 57696b56e91de2d60675df35587fe7aa4a756529 (patch) | |
| tree | 7229818b129cf0c35898886a58574b5cab6cf901 /src/http/ngx_http_request.c | |
| parent | 76605fa07a0b9579e00952528eb7dc455fa98d01 (diff) | |
| download | nginx-57696b56e91de2d60675df35587fe7aa4a756529.tar.gz nginx-57696b56e91de2d60675df35587fe7aa4a756529.zip | |
Added sending of extra CONNECTION_CLOSE frames.
According to quic-transport draft 28 section 10.3.1:
When sending CONNECTION_CLOSE, the goal is to ensure that the peer
will process the frame. Generally, this means sending the frame in a
packet with the highest level of packet protection to avoid the
packet being discarded. After the handshake is confirmed (see
Section 4.1.2 of [QUIC-TLS]), an endpoint MUST send any
CONNECTION_CLOSE frames in a 1-RTT packet. However, prior to
confirming the handshake, it is possible that more advanced packet
protection keys are not available to the peer, so another
CONNECTION_CLOSE frame MAY be sent in a packet that uses a lower
packet protection level.
Diffstat (limited to 'src/http/ngx_http_request.c')
0 files changed, 0 insertions, 0 deletions