GitHub encourages forking. The Git repository you cited is a fork that differs from your Debian package. Assuming that you are using libapache2-mod-rpaf for Debian wheezy, inspect libapache2-mod-rpaf_0.6-7+wheezy1.dsc.
Format: 3.0 (quilt)
Source: libapache2-mod-rpaf
Binary: libapache2-mod-rpaf
Architecture: any
Version: 0.6-7+wheezy1
Maintainer: Sergey B Kirpichev <skirpichev@gmail.com>
Dm-Upload-Allowed: yes
Homepage: http://stderr.net/apache/rpaf/
Standards-Version: 3.9.3
Vcs-Browser: http://git.debian.org/?p=collab-maint/libapache2-mod-rpaf.git;a=summary
Vcs-Git: git://git.debian.org/git/collab-maint/libapache2-mod-rpaf.git
Build-Depends: apache2-threaded-dev, debhelper (>= 9)
Package-List:
libapache2-mod-rpaf deb httpd extra
First, you may notice that http://stderr.net/apache/rpaf/ is a dead link. It's not clear that the package is well supported upstream.
Next, try inspecting the Vcs-Browser URL, then browse tree
→ mod_rpaf-2.0.c
. At Line 207, you'll see
static const command_rec rpaf_cmds[] = {
AP_INIT_FLAG(
"RPAFenable",
rpaf_enable,
NULL,
RSRC_CONF,
"Enable mod_rpaf"
),
AP_INIT_FLAG(
"RPAFsethostname",
rpaf_sethostname,
NULL,
RSRC_CONF,
"Let mod_rpaf set the hostname from X-Host header and update vhosts"
),
AP_INIT_ITERATE(
"RPAFproxy_ips",
rpaf_set_proxy_ip,
NULL,
RSRC_CONF,
"IP(s) of Proxy server setting X-Forwarded-For header"
),
AP_INIT_TAKE1(
"RPAFheader",
rpaf_set_headername,
NULL,
RSRC_CONF,
"Which header to look for when trying to find the real ip of the client in a proxy setup"
),
{ NULL }
};
Those are the directives that are relevant for the mod_rpaf 0.6 that comes with Debian wheezy.