Not able to set Default Header

[NickNaitik]

Hi, 

I am trying to send x-request-id header from my microservice while hitting the apigee endpoint but because x-request-id is the default header of apigee, while calling the downstream it overriding the x-request-id with some uuid by itself, Is there any way to stop populating default headers in apigee.

Thanks

[dchiesa1]

Hmmm, I understand. Let me see if I can get some other experts to have a look at this. 

[dchiesa1]

What version of Apigee are you using?

https://cloud.google.com/apigee/docs/release-notes#October_24_2022

There was a known issue related to overwriting x-request-id, but that was fixed long ago.  If you still have this problem, can you connect with the Support team and provide clear instructions for how to reproduce this behavior?

[Nick9]

I can see while i am getting request from microservice, it is having desired value but when its reaching to target it is changing, I think we need to set default header as false, somewhere in js.

[dchiesa1]

while i am getting request from microservice, it is having desired value ....

"while I am getting" - means the request as it is received by Apigee?

but when its reaching to target it is changing, I think we need to set default header as false, somewhere in js.

I think if the header is the correct value in the request that is RECEIVED BY your Apigee proxy, then you are not affected by that item I cited which was fixed in October 2022.

The next thing you should do is verify that the Header Apigee sends OUT, is correct. For any API request Apigee handles as a proxy, there are two distinct HTTP calls. One inbound, and one outbound, to the upstream service. In the default behavior, Apigee sends the same headers OUT s it received IN. Of course it is possible for you to use various policies in your API Proxy execution to modify the headers, or the payload, or the verb. So you need to check that Apigee is sending out, the expected value of the header.

If THAT is happening, and yet your target is NOT seeing that expected header value, then something external to Apigee, something between Apigee and your target, is modifying the header. To resolve that, you would need to investigate the network data path.