On Sat, Oct 13, 2012 at 7:41 AM, pangj pa...@riseup.net wrote:
In nginx's config file we have added the x-forwarded-for header.
With modperl (MP2) how to get this header?
Use headers_in():
http://perl.apache.org/docs/2.0/api/Apache2/RequestRec.html#C_headers_in_
- Perrin
On Mon, Oct 15, 2012 at 8:25 AM, Perrin Harkins per...@elem.com wrote:
On Sat, Oct 13, 2012 at 7:41 AM, pangj pa...@riseup.net wrote:
In nginx's config file we have added the x-forwarded-for header.
With modperl (MP2) how to get this header?
Use headers_in():
http://perl.apache.org/docs
the x-forwarded-for header.
With modperl (MP2) how to get this header?
Use headers_in():
http://perl.apache.org/docs/2.0/api/Apache2/RequestRec.html#C_headers_in_
As an alternative, you could use something like mod_rpaf on your backend
apache server:
http://stderr.net/apache/rpaf
Hi,
We have nginx as the reverse proxy in front of apache modperl servers.
In nginx's config file we have added the x-forwarded-for header.
With modperl (MP2) how to get this header? I have forgot that.
Thanks.
IIRC, it's not needed for mp2, since it's been implemented directly in
mod_proxy
Issac
Jonathan Vanasco wrote:
my mp2 needs to get the ip of the remote address
on some installations, mp2 is on port 80
on other installations, mp2 is on 80xx and the ip is in X-Forwarded-For
i'd like
Jonathan Vanasco [EMAIL PROTECTED] [04-08-2006 04:04]:
thanks for the info. i just said screwit and i wrote a new module.
[...]
would people be so kind as to look it up and give me some feedback?
It lacks IPv6 support.
--
Radosław Zieliński [EMAIL PROTECTED]
pgpdywpVT7EAx.pgp
Description:
On Aug 4, 2006, at 3:09 AM, Issac Goldstand wrote:
IIRC, it's not needed for mp2, since it's been implemented directly in
mod_proxy
the basic add/deny based on ips is. there is no x-forwarded-for
munging in it -- i searched the 2.059 source. it only adds headers
on a reverse proxy. i'll
On Fri, 2006-08-04 at 10:09 +0300, Issac Goldstand wrote:
IIRC, it's not needed for mp2, since it's been implemented directly in
mod_proxy
You are correct, but you're thinking of a different thing. That's the
part that adds the X-Forwarded-For header, which you used to need a
patch
On Aug 4, 2006, at 3:26 PM, Perrin Harkins wrote:
What Apache::ForwardedFor does is just run on the mod_perl side, read
the X-ForwardedFor header, and set the remote IP value to fake out
code
that runs after it.
so what do you think is more appropriate?
me uploading it to CPAN as a
On Fri, 2006-08-04 at 15:33 -0400, Jonathan Vanasco wrote:
so what do you think is more appropriate?
me uploading it to CPAN as a standalone, or gifting it to mod_perl?
Keep it on CPAN for now. I don't think it's commonly needed. If people
seem to be looking for it frequently, we can fold
the last version include feigned
support for X-Forwarded-Server by allowing multiple values for an
additionally required header.
I hope others find this useful.
my mp2 needs to get the ip of the remote address
on some installations, mp2 is on port 80
on other installations, mp2 is on 80xx and the ip is in X-Forwarded-For
i'd like to ensure that i pull the ip off the right place, under the
right conditions. all of my get_ip() calls happen
Jonathan Vanasco wrote:
my mp2 needs to get the ip of the remote address
on some installations, mp2 is on port 80
on other installations, mp2 is on 80xx and the ip is in X-Forwarded-For
You could re-write the remote IP at an early stage - add a
PerlFixupHandler or PerlTransHandler which
On Fri, 4 Aug 2006, John ORourke wrote:
Jonathan Vanasco wrote:
my mp2 needs to get the ip of the remote address
on some installations, mp2 is on port 80
on other installations, mp2 is on 80xx and the ip is in X-Forwarded-For
You could re-write the remote IP at an early stage - add
hooks
i think about 5 lines are the same :)
the big improvements ( i think ) are this:
a- specify the x-forwarded-for header name
b- specify a required additional header + value ( say you want to
embed x-forwarded-by='modperllist' on your gateway , to make sure its
an internal item
15 matches
Mail list logo
