ius-coredev team mailing list archive

[Jason Garber <boss@xxxxxxxxxx>]

Hi BJ,

Thank you for the effort on this (and the others)!  No problem - we'll see
what happens.  I'd be much more comfortable having a stable upstream as
well.

Thanks!
JasoN Garber

On Tue, May 18, 2010 at 5:05 PM, BJ Dierkes
<wdierkes@xxxxxxxxxxxxxxxxxxx>wrote:

> Jason,
>
> Since mod_rpaf doesn't exist in RHEL or EPEL, this package is more
> suited for EPEL.  I looked into the package and put a significant amount
> of work into improving the build structure of the source.  That said, I
> attempted to contact the maintainer which I haven't heard back from....
> making me a little weary of committing to support a package en-distro
> without the support of upstream.
>
> I'm going to sit on this a bit longer just to see if upstream replies.
>
> Thank you!
>
> ** Changed in: ius
>       Status: New => Triaged
>
> ** Changed in: ius
>     Assignee: (unassigned) => BJ Dierkes (derks)
>
> ** Changed in: ius
>   Importance: Undecided => Wishlist
>
> --
> new package: mod_rpaf
> https://bugs.launchpad.net/bugs/576752
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in IUS Community Project: Triaged
>
> 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 unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ius/+bug/576752/+subscribe
>

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

Status in IUS Community Project: Triaged

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.