upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-04-15 21:59:41 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

DOC: configuration: confuse "strict-mode" with "zero-warning"

Browse source 
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.
This commit is contained in:
William Lallemand 2025-08-28 17:31:27 +02:00
parent 21f7974e05
commit e0ec01849f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/configuration.txt
View file

@ -1272,8 +1272,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.