When running a reverse proxy in front of ERDDAP (e.g. nginx, load balancer etc.) the ip address recorded in the tomcat log files is an the internal proxy ip address, not the ip address of the client.
This PR adds requestAttributesEnabled="true" to AccessLogValve in server.xml after it is copied from the unidata tomcat image.
I don't think this should break anything, but definitely want to test this one out before merging. I have not previously worked with reverse proxies and request headers.
When running a reverse proxy in front of ERDDAP (e.g. nginx, load balancer etc.) the ip address recorded in the tomcat log files is an the internal proxy ip address, not the ip address of the client.
This PR adds
requestAttributesEnabled="true"
toAccessLogValve
inserver.xml
after it is copied from the unidata tomcat image.I don't think this should break anything, but definitely want to test this one out before merging. I have not previously worked with reverse proxies and request headers.
Solution first posted in the ERDDAP google group https://groups.google.com/g/erddap/c/8UUUSwavsvA/m/23-ClxdbAgAJ