diff options
| author | Roman Arutyunyan <arut@nginx.com> | 2021-08-05 09:20:32 +0300 |
|---|---|---|
| committer | Roman Arutyunyan <arut@nginx.com> | 2021-08-05 09:20:32 +0300 |
| commit | dab9163a95cb9c1c00ee9a3644c58474528b0f2b (patch) | |
| tree | 095ec68bffcf70e1f4d32f4d1508c1ca7442b60d /src/http/v3/ngx_http_v3_request.c | |
| parent | 0b179efeb0bc18e92a31748685cc74240ddb5667 (diff) | |
| download | nginx-dab9163a95cb9c1c00ee9a3644c58474528b0f2b.tar.gz nginx-dab9163a95cb9c1c00ee9a3644c58474528b0f2b.zip | |
QUIC: asynchronous shutdown.
Previously, when cleaning up a QUIC stream in shutdown mode,
ngx_quic_shutdown_quic() was called, which could close the QUIC connection
right away. This could be a problem if the connection was referenced up the
stack. For example, this could happen in ngx_quic_init_streams(),
ngx_quic_close_streams(), ngx_quic_create_client_stream() etc.
With a typical HTTP/3 client the issue is unlikely because of HTTP/3 uni
streams which need a posted event to close. In this case QUIC connection
cannot be closed right away.
Now QUIC connection read event is posted and it will shut down the connection
asynchronously.
Diffstat (limited to 'src/http/v3/ngx_http_v3_request.c')
0 files changed, 0 insertions, 0 deletions