From: Amaury Denoyelle Date: Wed, 5 Aug 2026 09:19:33 +0000 (+0200) Subject: DOC: explain better that named defaults are preserved X-Git-Tag: v3.5-dev4~7 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9de70ab31f0acbdfda96c09409f697ecf94095f5;p=thirdparty%2Fhaproxy.git DOC: explain better that named defaults are preserved Named defaults section are now kept after configuration by default. This behavior change has already been explained in "tune.defaults.purge". Mention again this change directly in "defaults" documentation. This is the main entry point documentation for "defaults" sections, so the change is now more visible to users. This should be backported up to 3.4. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 545907a6a..edffc7c26 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -5936,6 +5936,10 @@ of defaults sections. This can be convenient to establish certain configuration profiles to carry groups of default settings (e.g. TCP vs HTTP or short vs long timeouts) but can quickly become confusing to follow. +By default, named defaults sections are preserved after configuration parsing. +This allows to reuse them for dynamic backends creation. This behavior can be +changed globally via "tune.defaults.purge" keyword. + All proxy names must be formed from upper and lower case letters, digits, '-' (dash), '_' (underscore) , '.' (dot) and ':' (colon). ACL names are case-sensitive, which means that "www" and "WWW" are two different proxies.