QUIC: disabled bidirectional SSL shutdown after 09fb2135a589.

On QUIC connections, SSL_shutdown() is used to call the send_alert callback
to send a CONNECTION_CLOSE frame.  The reverse side is handled by other means.
At least BoringSSL doesn't differentiate whether this is a QUIC SSL method,
so waiting for the peer's close_notify alert should be explicitly disabled.

diff --git a/src/event/ngx_event_quic.c b/src/event/ngx_event_quic.c
index 7923c55293996e510df387bcc2ba7a74e847a166..918e8f716b7e23323f85fa6db25319fc6d5a48fb 100644 (file)
--- a/src/event/ngx_event_quic.c
+++ b/src/event/ngx_event_quic.c
@@ -2918,6 +2918,7 @@ ngx_quic_crypto_input(ngx_connection_t *c, ngx_quic_frame_t *frame, void *data)
                        "quic handshake completed successfully");
 
         c->ssl->handshaked = 1;
+        c->ssl->no_wait_shutdown = 1;
 
         frame = ngx_quic_alloc_frame(c, 0);
         if (frame == NULL) {