Envoy matches raw request paths, whereas servlet backends like Apache Tomcat strip semicolon matrix parameters from each path segment before resource resolution. The `ignore path parameters in path matching` option truncates at the first semicolon, failing to replicate the per-segment behavior of the backend. A remote client can exploit this by using a parameterized protected segment or a parameter on an earlier segment, causing Envoy to select an unprotected fallback while the backend resolves the protected resource. This bypass occurs when a path-based decision is made by Envoy and the backend strips semicolon parameters per segment.