Werk #22334: Analyze configuration: Fix false WARN on Apache X-Forwarded headers
| Component | Setup | ||||
| Title | Analyze configuration: Fix false WARN on Apache X-Forwarded headers | ||||
| Date | Nov 10, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
The test Apache X-Forwarded-Proto/-Ssl headers in Setup > Maintenance >
Analyze configuration, introduced with Werk #22268, searched the files below
/etc/apache2 and /etc/httpd for the header names. It reported WARN when
the names only appeared in a comment or in a configuration file that is not
enabled. With APACHE_FORWARDED_HEADERS set to manual it reported WARN
when a proxy or load balancer on another host sets the headers, although that
is the setup manual is meant for.
The test no longer reads the Apache configuration. It now checks whether the
request that runs it reaches the site with an X-Forwarded-Proto header:
auto:WARNif the header is missing. Runomd update-apache-config SITEas root and make sure the Apache module mod_headers is enabled. If the site is not reached through the system Apache, e.g. in a container, the proxy in front of it has to set the header.manual:WARNif the header is missing. The proxy or load balancer in front of the system Apache has to set it.
A RequestHeader directive left over from a manual setup is no longer
reported in auto mode. Checkmk's own directive takes precedence, so the
leftover does no harm.
The test is no longer executed on the remote sites of a distributed setup. There it would only see the request of the central site, which need not take the same way as the requests of the remote site's clients.