Nginx + apache : REMOTE_ADDR and REMOTE_HOST bug
Albuquerque Rui
saiaman01 at gmail.com
Tue Aug 30 18:29:44 UTC 2011
2011/8/30 Jim Ohlstein <jim at ohlste.in>
> On 8/30/11 12:47 PM, Albuquerque Rui wrote:
> > proxy_set_header Host $host;
> > proxy_set_header X-Real-IP $remote_addr;
> > proxy_set_header X-Forwarded-For
> > $proxy_add_x_forwarded_for;
> >
> >
> >
> > And on apache :
> >
> > LoadModule rpaf_module modules/mod_rpaf-2.0.so <http://mod_rpaf-2.0.so>
> > RPAFenable On
> > RPAFsethostname On
> > RPAFproxy_ips 127.0.0.1
> > RPAFheader X-Forwarded-For
>
>
> Please do not top post. It makes following a thread much more difficult.
>
> We use the following in Apache:
>
> RPAFenable On
> RPAFsethostname On
> RPAFproxy_ips 127.0.0.1
>
> First thing I would suggest is running a phpinfo script and seeing what
> the value of _SERVER["REMOTE_ADDR"] is.
>
>> Changes done, nothing changed.. Still the same problem...The fact is that
it seems mod_rpaf is working well because REMOTE_ADDR is good, but
REMOTE_HOST is not good :( :( :(
>
> Then comment out the line that begins with "RPAF header", restart Apache
> and run again and see if the value changes.
>
>
> >
> >
> >
> >
> >
> >
> > 2011/8/30 Jim Ohlstein <jim at ohlste.in <mailto:jim at ohlste.in>>
> >
> > On 8/30/11 12:23 PM, Albuquerque Rui wrote:
> > > Yes that's right. It's really strange that i'm the only one having
> > this
> > > problem with mod_rpaf 0.6 :( :( :(
> > >
> > >
> > > 2011/8/30 Maxim Dounin <mdounin at mdounin.ru
> > <mailto:mdounin at mdounin.ru> <mailto:mdounin at mdounin.ru
> > <mailto:mdounin at mdounin.ru>>>
> > >
> > > Hello!
> > >
> > > On Tue, Aug 30, 2011 at 06:06:37PM +0200, Albuquerque Rui
> wrote:
> > >
> > > > Hello,
> > > > i've got a "funny" bug.
> > > >
> > > > My installation is Nginx 1.0 and apache ( httpd ) behind.
> > > >
> > > > Apache got's mod_rpaf activated and HostNameLookups On.
> > > >
> > > > When testing a php script i find this problem :
> > > >
> > > > _SERVER["REMOTE_HOST"]************<= my webserver hostname
> > > > _SERVER["REMOTE_ADDR"]82.125.151.3<= my ip
> > >
> > > I.e. client's ip is correct, but client's hostname still points
> to
> > > your webserver, right? This looks like problem in mod_rpaf.
> >
> > It looks like it's reporting *his* IP, not that of the client and
> Apache
> > is doing a look up on that IP?
> >
> > How are you passing the remote IP from nginx to Apache?
> >
> >
> > >
> > > Maxim Dounin
> > >
> > > _______________________________________________
> > > nginx mailing list
> > > nginx at nginx.org <mailto:nginx at nginx.org>
> > <mailto:nginx at nginx.org <mailto:nginx at nginx.org>>
> > > http://mailman.nginx.org/mailman/listinfo/nginx
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > nginx mailing list
> > > nginx at nginx.org <mailto:nginx at nginx.org>
> > > http://mailman.nginx.org/mailman/listinfo/nginx
> >
> >
> > --
> > Jim Ohlstein
> >
> > _______________________________________________
> > nginx mailing list
> > nginx at nginx.org <mailto:nginx at nginx.org>
> > http://mailman.nginx.org/mailman/listinfo/nginx
> >
> >
> >
> >
> > _______________________________________________
> > nginx mailing list
> > nginx at nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
>
> --
> Jim Ohlstein
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20110830/dc0ab93e/attachment.html>
More information about the nginx
mailing list