Apache Server configuration support - Trouble with getting REMOTE_ADDR in Apache2 + mod_security from frontend reverse proxy

This is Interesting: Free IT Magazines  
Home > Archive > Apache Server configuration support > August 2007 > Trouble with getting REMOTE_ADDR in Apache2 + mod_security from frontend reverse proxy





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Trouble with getting REMOTE_ADDR in Apache2 + mod_security from frontend reverse proxy
Vladimir

2007-08-17, 1:21 am

I use Nginx (listen IP x.x.x.x) as frontend and Apache-2.2.4 (listen
IP 127.0.0.1) + mod_security-2.1.1-r1 as backend. OS Gentoo Linux.
Mod_rpaf get "X-Forwarded-For" from Nginx and set REMOTE_ADDR from it
on Apache.
Apache see all requests as real clients IP.
But mod_security don't see this new REMOTE_ADDR. Mod_security see all
requests as from 127.0.0.1 and they can't be filtrable by client IP
conditions.

The same configuration with Nginx, Apache-1.3.37 and
mod_security-1.9.4 works fine.

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2009 webservertalk.com