Hello all,
I'm not sure, but it seems to me that in the doc/configuration.txt
documentation, the paragraph related to the keyword
tune.ssl.ssl-ctx-cache-size was also copied for the description of
the keyword tune.ssl.ocsp-update.mindelay:
tune.ssl.ssl-ctx-cache-size <number>
Sets the size of the cache used to store generated certificates to <number>
entries. This is a LRU cache. Because generating a SSL certificate
dynamically is expensive, they are cached. The default cache size is set to
1000 entries.
tune.ssl.ocsp-update.mindelay <number>
..
Sets the size of the cache used to store generated certificates to <number>
entries. This is a LRU cache. Because generating a SSL certificate
dynamically is expensive, they are cached. The default cache size is set to
1000 entries.
If this is not the case, please ignore this patch.
Best regards,
--
Miroslav Zagorac
Senior Developer
From dd98f4162ce15110bd71eeaf55eafe923dda3c77 Mon Sep 17 00:00:00 2001
From: Miroslav Zagorac <mzago...@haproxy.com>
Date: Tue, 9 Jan 2024 20:55:47 +0100
Subject: [PATCH] DOC: configuration: corrected description of keyword
tune.ssl.ocsp-update.mindelay
Deleted the text paragraph in the description of keyword
tune.ssl.ocsp-update.mindelay, which was added in the commit 5843237
"MINOR: ssl: Add global options to modify ocsp update min/max delay",
because it was a copy of the description of tune.ssl.ssl-ctx-cache-size.
---
doc/configuration.txt | 5 -----
1 file changed, 5 deletions(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 406a6bb01..6585288b4 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -3905,11 +3905,6 @@ tune.ssl.ocsp-update.mindelay <number>
"tune.ssl.ocsp-update.maxdelay". See option "ocsp-update" for more
information about the auto update mechanism.
- Sets the size of the cache used to store generated certificates to <number>
- entries. This is a LRU cache. Because generating a SSL certificate
- dynamically is expensive, they are cached. The default cache size is set to
- 1000 entries.
-
tune.stick-counters <number>
Sets the number of stick-counters that may be tracked at the same time by a
connection or a request via "track-sc*" actions in "tcp-request" or
--
2.42.0
