Re: Can't get RemoteIpValve to work

2023-03-29 Thread Leon Rosenberg
Thanks, yes I think my problem never was with the RemoteIpValve, and the other project I copied configuration from actually didn't work despite me thinking it did ;) kr Leon On Wed, Mar 29, 2023 at 6:45 AM Mark Thomas wrote: > On 28/03/2023 21:08, Leon Rosenberg wrote: > > Sorry it took a

Re: Can't get RemoteIpValve to work

2023-03-28 Thread Mark Thomas
On 28/03/2023 21:08, Leon Rosenberg wrote: Sorry it took a little longer. Turns out that the actual RemoteIpValve works correctly, but the *Access Log Valve *doesn't. We were primarily looking into the localhost_access*logs, hence the confusion: Headers with RemoteIpValue on: header: host;

Re: Can't get RemoteIpValve to work

2023-03-28 Thread Leon Rosenberg
Sorry it took a little longer. Turns out that the actual RemoteIpValve works correctly, but the *Access Log Valve *doesn't. We were primarily looking into the localhost_access*logs, hence the confusion: Headers with RemoteIpValue on: header: host; value: api.myhost.com header: user-agent; value:

Re: Can't get RemoteIpValve to work

2023-03-25 Thread Christopher Schultz
Leon, On 3/24/23 10:09, Leon Rosenberg wrote: Full log output (dumping out headers, without the valve): 6049752 2023-03-24 14:07:59,749 [http-apr-8080-exec-13] INFO n.a.c.extapi.ping.PingResource:38 - key: host; value: api.myhost.net 6049752 2023-03-24 14:07:59,749 [http-apr-8080-exec-13] INFO

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Mark Thomas
And if you dump out the headers and the value of ServletRequest.getRemoteAddr() with (and without for completeness) the RemoteIpValve ? Mark On 24/03/2023 14:09, Leon Rosenberg wrote: Full log output (dumping out headers, without the valve): 6049752 2023-03-24 14:07:59,749

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Leon Rosenberg
Full log output (dumping out headers, without the valve): 6049752 2023-03-24 14:07:59,749 [http-apr-8080-exec-13] INFO n.a.c.extapi.ping.PingResource:38 - key: host; value: api.myhost.net 6049752 2023-03-24 14:07:59,749 [http-apr-8080-exec-13] INFO n.a.c.extapi.ping.PingResource:38 - key:

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Leon Rosenberg
yeah, interestingly enough removing ipvalve and adding access log magic, puts the X-Forwarded-For in the localhost_access.log ... but strange nevertheless. On Fri, Mar 24, 2023 at 11:44 AM Mark Thomas wrote: > Maybe try commenting out the RemoteIpValve in Tomcat and retest so you > can see

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Leon Rosenberg
Hi Konstantin, Server version: Apache Tomcat/9.0.64 Server built: Jun 2 2022 19:08:46 UTC Server number: 9.0.64.0 OS Name:Linux OS Version: 5.4.0-1092-gcp Architecture: amd64 JVM Version:1.8.0_332-b09 JVM Vendor: Temurin kr Leon On Fri, Mar 24, 2023 at 1:17 PM

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Konstantin Kolinko
пт, 24 мар. 2023 г. в 13:30, Leon Rosenberg : > > Hi, > > we have following setup > apache 2.4 on a ubuntu host, in front of docker-container with tomcat9 (on > same host). > Connection is via apache mod_http/proxy. > > Internal IP of the host is 10.138.0.3 (where httpd and docker are running). >

Re: Can't get RemoteIpValve to work

2023-03-24 Thread Mark Thomas
Maybe try commenting out the RemoteIpValve in Tomcat and retest so you can see exactly what headers Tomcat is seeing. Alternatively, since this is over http, Wireshark or similar could help. Mark On 24/03/2023 10:29, Leon Rosenberg wrote: Hi, we have following setup apache 2.4 on a ubuntu

Can't get RemoteIpValve to work

2023-03-24 Thread Leon Rosenberg
Hi, we have following setup apache 2.4 on a ubuntu host, in front of docker-container with tomcat9 (on same host). Connection is via apache mod_http/proxy. Internal IP of the host is 10.138.0.3 (where httpd and docker are running). In localhost_access log we see always 10.138.0.3 address. If