Dave,
On 2/15/16 12:31 PM, Dave Fisher wrote:
> You can take the source code for RemoteIPFilter and have it look at the
> X-Forwarded-For header.
>
> Even better offer a patch to RemoteIPFilter to allow the header field name to
> be configured.
>
> You are not the only one with this use case.
You can take the source code for RemoteIPFilter and have it look at the
X-Forwarded-For header.
Even better offer a patch to RemoteIPFilter to allow the header field name to
be configured.
You are not the only one with this use case.
Regards,
Dave
Sent from my iPhone
> On Feb 15, 2016, at 7
On 15.02.2016 13:03, Dhanushka Parakrama wrote:
Hi Guys
I have a Tomcat instance behind the load balancer (LB) , LB will pass the
client ip address to backed tomcat instance using *X-forward-for* header .
I basically want to filter user traffic based on the *X-forwaed-for* header
in tomcat ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dhanushka,
On 2/15/16 7:03 AM, Dhanushka Parakrama wrote:
> I have a Tomcat instance behind the load balancer (LB) , LB will
> pass the client ip address to backed tomcat instance using
> *X-forward-for* header .
Note that the HTTP header is actuall
Hi Guys
I have a Tomcat instance behind the load balancer (LB) , LB will pass the
client ip address to backed tomcat instance using *X-forward-for* header .
I basically want to filter user traffic based on the *X-forwaed-for* header
in tomcat instance
i have configured the following filter in t
