Currently if a loadbalancer is present the servers IP is sent and processed,
which of course makes no sense whatsever. In the loadbalancer sends the
X_FORWARDED_FOR header the authnz_external cannot handle it though. I wrote a
small patch which sends the X_FORWADED_FOR header to the client in the PROXY
environment variable
Here's the diff:
diff mod_authnz_external-3.2.6-new/mod_authnz_external.c
mod_authnz_external-3.2.6/mod_authnz_external.c
100d99
< #define ENV_PROXY "PROXY"
438c437
< char *child_env[13];
---
> char *child_env[12];
461c460
< const char *cookie, *host, *remote_host, *proxy;
---
> const char *cookie, *host, *remote_host;
498,499d496
< if ((proxy= apr_table_get(r->headers_in, "X-Forwarded-For")) != NULL)
< child_env[i++]= apr_pstrcat(p, ENV_PROXY"=", proxy, NULL);
Original issue reported on code.google.com by rogier.s...@gmail.com on 19 Aug 2013 at 1:41
Original issue reported on code.google.com by
rogier.s...@gmail.com
on 19 Aug 2013 at 1:41