From: William Lallemand Date: Thu, 28 Aug 2025 15:31:27 +0000 (+0200) Subject: DOC: configuration: confuse "strict-mode" with "zero-warning" X-Git-Tag: v3.0.12~52 X-Git-Url: http://git.haproxy.org/?a=commitdiff_plain;h=0d49f26266e1d66dac59fb8822bd6425f4bc9aa2;p=haproxy-3.0.git DOC: configuration: confuse "strict-mode" with "zero-warning" 4b10302fd8 ("MINOR: cfgparse: implement a simple if/elif/else/endif macro block handler") introduces a confusion between "strict-mode" and "zero-warning". This patch fixes the issue by changing "strict-mode" by "zero-warning" in section 2.4. Conditional blocks. Must be backported as far as 2.4. (cherry picked from commit e0ec01849fc6eff6a6e9ac67e23dea03d779fe70) Signed-off-by: Christopher Faulet (cherry picked from commit 98d4d720e11ef808e849bba76e902fee7f6419d1) Signed-off-by: Christopher Faulet (cherry picked from commit 46cf247231358866b5c6c03e0176f7e5290a2492) Signed-off-by: Christopher Faulet --- diff --git a/doc/configuration.txt b/doc/configuration.txt index a3429cb..c0aeec8 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -1143,8 +1143,8 @@ Four other directives are provided to report some status: - .warning "message" : emit this message at level WARNING - .alert "message" : emit this message at level ALERT -Messages emitted at level WARNING may cause the process to fail to start if the -"strict-mode" is enabled. Messages emitted at level ALERT will always cause a +Messages emitted at level WARNING may cause the process to fail to start if +"zero-warning" is enabled. Messages emitted at level ALERT will always cause a fatal error. These can be used to detect some inappropriate conditions and provide advice to the user.