APIGEE X headers not available in the request/response flows inside the proxy.

[darpanjain420]

I am trying to use x-apigee-message-id to be explicitly set in a header and sent to the backend target server api.
But when i use Assign message policy in the preflow of the proxy endpoint with "Ref = request.header.x-apigee-message-id" , I get empty value and in debug I can see none of the headers which were listed in the node "request received by client".
Kindly suggest as to what I may be missing. I just want to use one of the headers which I can see in the request node.

[ganadurai · Accepted solution]

Checkout this docs page. https://docs.apigee.com/migration-to-x/compare-apigee-edge-to-apigee-x#unsupported-features

Headers prefixed with "X-Apigee-" are not supported in Apigee X and are stripped from requests and responses before sending to targets and clients.

[ganadurai · Accepted solution]

Checkout this docs page. https://docs.apigee.com/migration-to-x/compare-apigee-edge-to-apigee-x#unsupported-features

Headers prefixed with "X-Apigee-" are not supported in Apigee X and are stripped from requests and responses before sending to targets and clients.

[darpanjain420]

If I want to use that header in the proxy itself and assign that to a variable and then create a new header using that variable. 

Should that not work?

The doc link you gave indicates that it is stripped before sending to the target and client right. But it does not say those are stripped in the proxy as well.

If at all the above is not possible, is there any other unique message id which I can use to send to the backend? 

[ganadurai · Accepted solution]

https://cloud.google.com/apigee/docs/api-platform/reference/variables-reference#messageid