quic_retry
The `quic_retry` directive enables or disables QUIC connection retry behavior in NGINX.
Description
The quic_retry directive is used to control the QUIC protocol's behavior regarding connection retries. When enabled, NGINX will respond to incoming connection requests that do not include a valid connection ID with a retry packet. This mechanism is crucial when clients have recently established connections that may not yet have been fully completed. By using connection retries, NGINX assists in managing situation where clients may experience dropped connections or transitions between networks, allowing them to reconnect seamlessly without extended delays.
The directive can take a boolean flag as its argument, with 'on' indicating that QUIC retries are permitted and 'off' indicating that they are not. This flexibility permits system administrators to enable or disable QUIC retry functionality based on their specific network environments or application demands. Within both http and server contexts, administrators can fine-tune their QUIC implementations, improving performance and reliability for users connecting over the QUIC protocol.
Config Example
http {
quic_retry on;
}
server {
listen 443 quic;
quic_retry on;
}Ensure QUIC is correctly configured in your NGINX setup before using this directive, as missing settings can lead to unexpected behavior.
Keep in mind that enabling quic_retry may increase the load on your server if clients frequently abandon connections.