Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

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

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.

Solved Solved
0 5 1,434
2 ACCEPTED SOLUTIONS

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.


 

View solution in original post

5 REPLIES 5

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.


 

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? 

We have come across similar issue. Whenever we tried to pass the header Proxy-Authorization it's not being sent and shown in the debug file. But if we use some random header for example test-header in the request we could see it in the trace. Issue only for apigee x. For edge we haven't seen the issue. In the doc I haven't found about the Proxy-Authorization. Is it something predefined one. Why it's not showing in the debug when we passing it on header. We sent a basic get call request  with header Proxy-Authorization. End point mock target. @dchiesa1 @@ganadurai @vidyutverma 


Yours is a new question. Don't ask new questions in comments on threads that are 18 months old.  I don't answer such questions.  Ask a new question, and I will answer there.