Svilen

@ankitm123 I am adding here the output of the PipelineActivity ``` apiVersion: jenkins.io/v1 kind: PipelineActivity metadata: annotations: lighthouse.jenkins-x.io/cloneURI: https://gitlab.our-company.com/our-group/our-company-data-protection/microservices/our-service.git lighthouse.jenkins-x.io/job: release creationTimestamp: "2022-07-14T09:18:19Z" generation: 15 labels: branch: main build: "10"...

@tao12345666333 this issue is a continuation of https://the-asf.slack.com/archives/CUC5MN17A/p1656432528471899

@tao12345666333, yes the request chain is correct.

Great. If I understand, you were able to reproduce it, right?

Hi, @tao12345666333, I will be glad to help you. Can you tell me how can I get this information for you?

FYI, currently istio mTLS is in permissive mode (the issue occurs only in strict mode) > Request routing directly in APISIX container, check its request and response headers ``` kubectl...

@tao12345666333 do you have any updates on this issue?

Our issue might be related with https://github.com/apache/apisix/issues/7573. I think if we have control on this header, it solve our issue with the mTLS as well.

I tried to edit the route and add the plugins section with the proxy-rewrite plugin, but I could manage to configure this plugin by adding: ``` "plugins": { "proxy-rewrite": {...

I have experienced similar problems with the [spotbugs-maven-plugins](https://github.com/spotbugs/spotbugs-maven-plugin).