mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-11-28 14:21:00 +01:00
Code Issues Projects Releases Wiki Activity

DOC: config: clarify log-forward "host" option

Browse Source 
log-forward "host" option may be confusing because we often mention the
host field when talking about syslog RFC3164 or RFC5424 messages, but
neither rfc actually define "host" field. In fact, everywhere we used
"host field" we actually meant "hostname field" as documented in RFC5424.
This was a language abuse on our side.

In this patch we replace "host" with "hostname" where relevant in the
documentation to prevent confusion.

Thanks to Nick Ramirez for having reported the issue.
This commit is contained in:
Aurelien DARRAGON 2025-04-28 12:09:45 +02:00
parent 385b3f923f
commit e921362810
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
doc/configuration.txt
View File

@ -5579,31 +5579,31 @@ option dont-parse-log
option host { replace | fill | keep | append }
Set the host strategy that should be used on the log-forward section
regarding syslog host field for outbound rfc3164 or rfc5424 messages.
regarding syslog hostname field for outbound rfc3164 or rfc5424 messages.
replace If input message already contains a value for the host field,
replace If input message already contains a value for the hostname field,
we replace it by the source IP address from the sender.
If input message doesn't contain a value for the host field (ie:
'-' as input rfc5424 message or non compliant rfc3164 or rfc5424
message), we use the source IP address from the sender as host
field.
fill If input message already contains a value for the host field,
we keep it.
If input message doesn't contain a value for the host field
If input message doesn't contain a value for the hostname field
(ie: '-' as input rfc5424 message or non compliant rfc3164 or
rfc5424 message), we use the source IP address from the sender as
host field.
hostname field.
fill If input message already contains a value for the hostname field,
we keep it.
If input message doesn't contain a value for the hostname field
(ie: '-' as input rfc5424 message or non compliant rfc3164 or
rfc5424 message), we use the source IP address from the sender as
hostname field.
(This is the default)
keep If input message already contains a value for the host field,
keep If input message already contains a value for the hostname field,
we keep it.
If input message doesn't contain a value for the host field,
If input message doesn't contain a value for the hostname field,
we set it to 'localhost' (rfc3164) or '-' (rfc5424).
append If input message already contains a value for the host field,
append If input message already contains a value for the hostname field,
we append a comma followed by the IP address from the sender.
If input message doesn't contain a value for the host field,
If input message doesn't contain a value for the hostname field,
we use the source IP address from the sender.
For all options above, if the source IP address from the sender is not