Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

Hi user group: just found open-telemetry has fixing for it: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/tomcat/tomcat-common/javaagent/src/main/java/io/opentelemetry/javaagent/instrumentation/tomcat/common/TomcatHelper.java#L71 ``` static Strin

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

Hi Mark I can't find any Valve setting in the spring boot application(search by valve), would you mind sharing more info? Regarding the mb state and debugging, yes aware that my local intellij debugger could change the mb state, so in the the debug lib I call mb.getType() only I got more interes

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

On 17/03/2023 14:27, Rui wrote: Hi user group: I added some debug info to the 9.0.71 baseline from the logs it hit this (supposed not inn 9.0.70) https://github.com/apache/tomcat/blob/9.0.71/java/org/apache/catalina/connector/CoyoteAdapter.java#L677 That suggests you are using the Rewrite Val

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

Hi user group: I added some debug info to the 9.0.71 baseline from the logs it hit this (supposed not inn 9.0.70) https://github.com/apache/tomcat/blob/9.0.71/java/org/apache/catalina/connector/CoyoteAdapter.java#L677 means undecodedURI type is T_CHARS or T_STR, however, decodedURI type is T_NUL

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

I did some tests with several different commits in 9.0.71, I think my issue is caused by this https://github.com/apache/tomcat/commit/10a1a6d46d952bab4dfde44c3c0de12b0330da79 the "toBytesSimple" change has not been added to the repo yet, so the change in 9.073 doesn't solve the problem. Next I will

RE: health check return 404 after upgrade from 70 to tomcat 9.0.71

> -Original Message- > From: Chuck Caldarale > Sent: Monday, March 6, 2023 1:12 PM > To: Tomcat Users List > Subject: Re: health check return 404 after upgrade from 70 to tomcat 9.0.71 > > > > On Mar 6, 2023, at 12:03, > wrote: > > > >

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

> On Mar 6, 2023, at 12:03, > wrote: > > I believe we may have figured out what was causing the issue, but not why it > was causing it. > > In the mod-proxy-http configuration for the balancer, we had been using the > fully qualified host name in the balancer url. When we switched to IP >

RE: health check return 404 after upgrade from 70 to tomcat 9.0.71

> -Original Message- > From: Mark Thomas > Sent: Monday, March 6, 2023 10:34 AM > To: users@tomcat.apache.org > Subject: Re: health check return 404 after upgrade from 70 to tomcat 9.0.71 > > On 25/02/2023 17:57, Mark Thomas wrote: > > > > > >

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

On 25/02/2023 17:57, Mark Thomas wrote: On 25/02/2023 15:47, Rui wrote: Hi recently upgraded tomcat to 9.0.71 from 9.0.70 but saw 404 in our EKS cluster(with istio installed) Received [GET /actuator HTTP/1.1 Host: x:8079 User-Agent: kube-probe/1.23+ Accept: */* Connection: close Accept-En

Re: health check return 404 after upgrade from 70 to tomcat 9.0.71

On 25/02/2023 15:47, Rui wrote: Hi recently upgraded tomcat to 9.0.71 from 9.0.70 but saw 404 in our EKS cluster(with istio installed) Received [GET /actuator HTTP/1.1 Host: x:8079 User-Agent: kube-probe/1.23+ Accept: */* Connection: close Accept-Encoding: gzip ] Incoming request /health

health check return 404 after upgrade from 70 to tomcat 9.0.71

Hi recently upgraded tomcat to 9.0.71 from 9.0.70 but saw 404 in our EKS cluster(with istio installed) Received [GET /actuator HTTP/1.1 Host: x:8079 User-Agent: kube-probe/1.23+ Accept: */* Connection: close Accept-Encoding: gzip ] Incoming request /health with originalRemoteAddr in 9.0.