Hi,
I found a some kind of glitch in Envoy logging. Is it by design?
We are using istio 1.18
I have a VirtualService bound to ingress-gateway with uri rewrite:
- match:
- uri:
prefix: "/cases-api/ws"
rewrite:
uri: "/ws"
route:
- destination:
host: "case-api.dmz.svc.cluster.local"
port:
number: 80
It works as expected, but Envoy logging show full path in both ends instead of rewrited one
Ingress-gateway outbound:
"GET /cases-api/ws HTTP/1.1" 400 - "-" 0 11 2 - "192.168.101.34,10.244.1.0" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36" "8b97eb7c-cca4-4241-a68f-c55f5b7f6a2c" "XXXX" "10.244.1.111:8080" outbound|80||case-api.dmz.svc.cluster.local - 10.244.4.81:443 10.244.1.0:42776 XXXX
Api Inbound
"GET /cases-api/ws HTTP/1.1" 400 - "-" 0 11 0 - "192.168.101.34,10.244.1.0" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36" "8b97eb7c-cca4-4241-a68f-c55f5b7f6a2c" "XXXX" "127.0.0.1:8080" inbound|80|http|case-api.dmz.svc.cluster.local - 10.244.1.111:8080 10.244.1.0:0 -