Setting remote addr to contents of header


#1

I’m running nginx beyind a L7 proxy (haproxy), I have haproxy setting
the X-Forwarded-For header and I’m using this to log the real IP of
the client and pass it to other processes that I’m proxying with nginx
(mongrels, apache, etc.). This works just great but I would like to be
able to use nginx directives to control access (allow, deny, etc.).
These don’t work since nginx itself sees the remote_addr as the IP of
the haproxy server.

Any suggestions? I would think a solution like mod_rpaf for apache
would be ideal.

Thanks,
Paul


#2

Hello!

On Wed, Apr 15, 2009 at 06:37:36PM -0400, Paul D. wrote:

I’m running nginx beyind a L7 proxy (haproxy), I have haproxy setting
the X-Forwarded-For header and I’m using this to log the real IP of
the client and pass it to other processes that I’m proxying with nginx
(mongrels, apache, etc.). This works just great but I would like to be
able to use nginx directives to control access (allow, deny, etc.).
These don’t work since nginx itself sees the remote_addr as the IP of
the haproxy server.

Any suggestions? I would think a solution like mod_rpaf for apache
would be ideal.

http://wiki.nginx.org/NginxHttpRealIpModule

Maxim D.


#3

The realip module only sets the X-Forwarded-For header based on an
upstream header. It doesn’t set the value of the client IP in the
nginx request object which is what is needed to get directives like
allow/deny to work.


#4

Paul D. wrote:

The realip module only sets the X-Forwarded-For header based on an
upstream header. It doesn’t set the value of the client IP in the
nginx request object which is what is needed to get directives like
allow/deny to work.

ngx_http_realip_module override client IP in the nginx request
object based on value from request header.

If allow/deny don’t work as need try to check set_real_ip_from and
real_ip_header settings.


#5

On Thu, Apr 16, 2009 at 4:20 AM, Maxim D. removed_email_address@domain.invalid
wrote:

Hello!

On Thu, Apr 16, 2009 at 12:52:01AM -0400, Paul D. wrote:

The realip module only sets the X-Forwarded-For header based on an
upstream header. It doesn’t set the value of the client IP in the
nginx request object which is what is needed to get directives like
allow/deny to work.

No, you are wrong. Try re-reading docs.

Thanks, I got it, it was my original mis-reading of the docs. I hadn’t
realized that set_real_ip_from had to be set at all times.

–Paul


#6

Hello!

On Thu, Apr 16, 2009 at 12:52:01AM -0400, Paul D. wrote:

The realip module only sets the X-Forwarded-For header based on an
upstream header. It doesn’t set the value of the client IP in the
nginx request object which is what is needed to get directives like
allow/deny to work.

No, you are wrong. Try re-reading docs.

Maxim D.