libapache2-mod-rpaf 0.5-3+squeeze1build0.8.04.1 source package in Ubuntu


libapache2-mod-rpaf (0.5-3+squeeze1build0.8.04.1) hardy-security; urgency=low

  * fake sync from Debian

libapache2-mod-rpaf (0.5-3+squeeze1) stable-security; urgency=high

  * New maintainer (See: #636732)
  * Edit 030_ipv6.patch to fix DOS via crafted X-Forwarded-For
    header (Closes: #683984, thanks to S├ębastien Bocahu)
 -- Steve Beattie <email address hidden>   Wed, 22 Aug 2012 16:17:50 -0700

Upload details

Uploaded by:
Steve Beattie on 2012-08-23
Uploaded to:
Original maintainer:
Sergey B Kirpichev
Very Urgent

See full publishing history Publishing

Series Pocket Published Component Section
Hardy updates on 2012-08-29 universe web
Hardy security on 2012-08-29 universe web


File Size MD5 Checksum
libapache2-mod-rpaf_0.5.orig.tar.gz 4.4 KiB 471fb059d6223a394f319b7c8ab45c4d
libapache2-mod-rpaf_0.5-3+squeeze1build0.8.04.1.diff.gz 7.6 KiB 2631ff466754bf3630757c9265aede34
libapache2-mod-rpaf_0.5-3+squeeze1build0.8.04.1.dsc 1.5 KiB f6d8e7fff15d57226a0e22d1f0923f25

View changes file

Binary packages built by this source

libapache2-mod-rpaf: module for Apache2 which takes the last IP from the 'X-Forwarded-For' header

 rpaf is short for reverse proxy add forward.
 rpaf is for backend Apache servers what mod_proxy_add_forward is for
 frontend Apache servers. It does exactly the opposite of
 mod_proxy_add_forward written by Ask Bjorn Hansen.
 It changes the remote address of the client visible to other Apache modules
 when two conditions are satisfied. First condition is that the remote client
 is actually a proxy that is defined in httpd.conf. Secondly if there is an
 incoming X-Forwarded-For header and the proxy is in its list of known
 proxies it takes the last IP from the incoming X-Forwarded-For header and
 changes the remote address of the client in the request structure.