From: Josh Soref Date: Mon, 23 May 2022 01:59:37 +0000 (-0400) Subject: spelling: every X-Git-Tag: dnsdist-1.8.0-rc3~10^2~21 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=14e9e4d3e1e250e8fc658db098dbb8f402a24bf5;p=thirdparty%2Fpdns.git spelling: every Signed-off-by: Josh Soref --- diff --git a/pdns/dnsdistdist/docs/advanced/tls-sessions-management.rst b/pdns/dnsdistdist/docs/advanced/tls-sessions-management.rst index 357587dd59..7f995cdf3a 100644 --- a/pdns/dnsdistdist/docs/advanced/tls-sessions-management.rst +++ b/pdns/dnsdistdist/docs/advanced/tls-sessions-management.rst @@ -69,7 +69,7 @@ For GnuTLS: Sessions management for outgoing connections -------------------------------------------- -Since 1.7, dnsdist supports securing the connection toward backends using DNS over TLS. For these connections, it keeps a cache of TLS tickets to be able to resume a TLS session quickly. By default that cache contains up to 20 TLS tickets per-backend, is cleaned up every every 60s, and TLS tickets expire if they have not been used after 600 seconds. +Since 1.7, dnsdist supports securing the connection toward backends using DNS over TLS. For these connections, it keeps a cache of TLS tickets to be able to resume a TLS session quickly. By default that cache contains up to 20 TLS tickets per-backend, is cleaned up every 60s, and TLS tickets expire if they have not been used after 600 seconds. These values can be set at configuration time via: * :func:`setOutgoingTLSSessionsCacheMaxTicketsPerBackend` diff --git a/pdns/dnsdistdist/docs/reference/config.rst b/pdns/dnsdistdist/docs/reference/config.rst index e3d238edf7..d7c41e7317 100644 --- a/pdns/dnsdistdist/docs/reference/config.rst +++ b/pdns/dnsdistdist/docs/reference/config.rst @@ -1716,7 +1716,7 @@ If you are looking for exact name matching, your might want to consider using a Outgoing TLS tickets cache management ------------------------------------- -Since 1.7, dnsdist supports securing the connection toward backends using DNS over TLS. For these connections, it keeps a cache of TLS tickets to be able to resume a TLS session quickly. By default that cache contains up to 20 TLS tickets per-backend, is cleaned up every every 60s, and TLS tickets expire if they have not been used after 600 seconds. +Since 1.7, dnsdist supports securing the connection toward backends using DNS over TLS. For these connections, it keeps a cache of TLS tickets to be able to resume a TLS session quickly. By default that cache contains up to 20 TLS tickets per-backend, is cleaned up every 60s, and TLS tickets expire if they have not been used after 600 seconds. These values can be set at configuration time via: .. function:: setOutgoingTLSSessionsCacheMaxTicketsPerBackend(num)