On Fri, Aug 11, 2023 at 10:49 AM Martin Vancl <[email protected]> wrote: > > No. As I wrote: > > I just updated to version 1.5.3 (from 1.4.0), and the problem is still the > > same. > So now I'm using 1.5.3 in docker. > > I wrote about version 1.3.0 in the first email three years ago.
Ah, okay - sorry to have missed that. I tried this out with the 1.5.3 container and adding the "-e REMOTE_IP_VALVE_ENABLED=true" option to the container creation command results in the following line being written to the server.xml file: <Valve className="org.apache.catalina.valves.RemoteIpValve"/> Can you confirm that you've created the container with that option and you're definitely not seeing that line?? There are additional properties that can be used to control the content of this line: PROXY_ALLOWED_IPS_REGEX - The IP regex that should show up as valid proxy addresses to Tomcat. PROXY_IP_HEADER - The HTTP header to use for the remote ip. PROXY_PROTOCOL_HEADER - The HTTP header to use for the protocol. PROXY_BY_HEADER - The HTTP header to use for the IP of the proxy that forwarded the request. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
