ius-coredev team mailing list archive

[bharper <576752@xxxxxxxxxxxxxxxxxx>]

Hey Jason,

I am doing a little house cleaning with old bugs.  It appears that BJ
never heard back from the maintainer nor has there been another release
of this module.  It would appear that this is a dead project.  I am
going to close out this bug.

-Ben

** Changed in: ius
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/576752

Title:
  WL: mod_rpaf

Status in IUS Community Project:
  Won't Fix

Bug description:
  This is a new package suggestion for IUS: mod_rpaf 0.6
  URL: http://stderr.net/apache/rpaf/

  This package was based on the IUS mod_wsgi SPEC file, adjusted to the
  needs of mod_rpaf.

  --
  mod_rpaf is for backend Apache servers what mod_proxy_add_forward is for frontend
  Apache servers. It does excactly the opposite of mod_proxy_add_forward written
  by Ask Bjørn Hansen. It will also work with mod_proxy in Apache starting with
  release 1.3.25 and mod_proxy that is distributed with Apache2 from version
  2.0.36.

  --
  Why does this matter?  When using apache as a backend server behind a proxy like nginx, all of the requests appear to originate from the IP of the proxy.  Server variables such as REMOTE_ADDR are also affected, breaking a lot of applications.

  mod_rpaf resolves that by allowing one to specify the following
  configuration directives which make apache think the request
  originated from where it actually came from, instead of the proxy.

  RPAFenable On
  RPAFsethostname On
  RPAFproxy_ips 127.0.0.1 192.168.1.13
  RPAFheader X-Forwarded-For

  --
  This package is an ACN rpm, and will need updated to be an IUS rpm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/576752/+subscriptions