Thanks for all the answers.
于 2012-10-15 7:39, Cees Hek 写道:
On Mon, Oct 15, 2012 at 8:25 AM, Perrin Harkins mailto:per...@elem.com>> wrote:
On Sat, Oct 13, 2012 at 7:41 AM, pangj mailto:pa...@riseup.net>> wrote:
> In nginx's config file we have added the x-forwarded-for header.
>
On Mon, Oct 15, 2012 at 8:25 AM, Perrin Harkins wrote:
> On Sat, Oct 13, 2012 at 7:41 AM, pangj 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/RequestRe
On Sat, Oct 13, 2012 at 7:41 AM, pangj 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 Aug 4, 2006, at 3:36 PM, Perrin Harkins wrote:
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 it in.
ok
Apache2::xForwardedFor is now in CPAN. should be visible shortly
Its version 0.02 - upgrades from the las
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
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 standa
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 for and no
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 po
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
Descrip
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 l
thanks for the info. i just said screwit and i wrote a new module.
Apache2::xForwardedFornication
or
Apache2::xForwardedFor
i took Apache::ForwardedFor , tried to port it, disliked a lot of
things, and decided this would be a good chance to just rewrite it
entirely and add some new hook
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 a PerlF
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 goe
13 matches
Mail list logo
