From e27216b79932c0dea14f6fec7aff84eda01d7245 Mon Sep 17 00:00:00 2001 From: Olivier Houchard Date: Tue, 25 Nov 2025 13:17:45 +0100 Subject: [PATCH] DOC: ssl: Note that 0rtt works fork QUIC with QuicTLS too. Document that one can use 0rtt with QUIC when using QuicTLS too. --- doc/configuration.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 422eaf6be..374c9de89 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -16513,10 +16513,10 @@ allow-0rtt you should only allow if for requests that are safe to replay, i.e. requests that are idempotent. You can use the "wait-for-handshake" action for any request that wouldn't be safe with early data. - With QUIC, 0rtt is supported with OpenSSL >= 3.5.2 and AWS-LC. With TCP/TLS, - 0rtt is only supported with OpenSSL, and requires that the client sends an - ALPN, otherwise the early data won't be considered before the handshake - happens. + With QUIC, 0rtt is supported with QuicTLS, OpenSSL >= 3.5.2 and AWS-LC. + With TCP/TLS, 0rtt is only supported with OpenSSL, and requires that the + client sends an ALPN, otherwise the early data won't be considered before + the handshake happens. alpn This enables the TLS ALPN extension and advertises the specified protocol @@ -17745,8 +17745,8 @@ allow-0rtt Allow sending early data to the server when using TLS 1.3. Note that early data will be sent only if the client used early data, or if the backend uses "retry-on" with the "0rtt-rejected" keyword. - With QUIC, 0rtt is supported with OpenSSL >= 3.5.2 and AWS-LC. With TCP/TLS, - 0rtt is only supported with OpenSSL. + With QUIC, 0rtt is supported with QuicTLS, OpenSSL >= 3.5.2 and AWS-LC. + With TCP/TLS, 0rtt is only supported with OpenSSL. alpn May be used in the following contexts: tcp, http