Hello, Please find attached a little patch for the "strict-sni" configuration documentation, which had incorrect grammar.
Best, ~Nicolas
>From 077761ca4b9b3b420ad1f635179cd747dfb7a8eb Mon Sep 17 00:00:00 2001 From: Nicolas CARPi <nico-git@deltablot.email> Date: Wed, 3 Apr 2024 13:43:59 +0200 Subject: [PATCH] DOC: configuration: grammar fixes for strict-sni Fix incorrect grammar in strict-sni: * is allow -> is allowed * which match -> that matches * allows to start -> allows starting --- doc/configuration.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 68af0a844..8ea0c50bd 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -16296,9 +16296,9 @@ ssl-min-ver [ SSLv3 | TLSv1.0 | TLSv1.1 | TLSv1.2 | TLSv1.3 ] strict-sni This setting is only available when support for OpenSSL was built in. The - SSL/TLS negotiation is allow only if the client provided an SNI which match + SSL/TLS negotiation is allowed only if the client provided an SNI that matches a certificate. The default certificate is not used. This option also allows - to start without any certificate on a bind line, so an empty directory could + starting without any certificate on a bind line, so an empty directory could be used and filled later from the stats socket. See the "crt" option for more information. See "add ssl crt-list" command in the management guide. -- 2.44.0
