Bug#807120: marked as done (Deprecate mod_rpaf, transition to mod_remoteip)
Your message dated Fri, 2 Dec 2022 14:33:06 +0100
with message-id <20221202143306.10f59a91@frustcomp.hnjs.home.arpa>
and subject line
has caused the Debian Bug report #807120,
regarding Deprecate mod_rpaf, transition to mod_remoteip
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
807120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807120
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Severity: important
mod_rpaf module has dead upstream (there are alternative
at https://github.com/gnif/mod_rpaf/) and has a good
candidate for replacement in the core modules:
http://httpd.apache.org/docs/2.4/mod/mod_remoteip.html
Probably, we must coordinate transition from mod_rpaf
to mod_remoteip and then remove mod_rpaf.
Default rpaf.conf could be replaced with:
<IfModule remoteip_module>
RemoteIPHeader X-Forwarded-For
RemoteIPTrustedProxy 127.0.0.1
</IfModule>
In general, this mapping should work:
RPAFheader <-> RemoteIPHeader
RPAFproxy_ips <-> RemoteIPTrustedProxy
To get CLF-type logs with proper client addresses we should use %a
instead of %h. Could we alter the default common log format entry?
--- End Message ---
--- Begin Message ---
Control: tag -1 fixed-upstream
mod_rpaf is in a separate package and current apache2 packages contain mod_remoteip.
The bug in the logformat hostname has been fixed upstream.
Therefore this bug is considered fixed.
--- End Message ---
Reply to: