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

Apigee X - Target URL is shown incorrectly in debug session if target.url variable is used

In the <HttpTargetConnection> in the TargetPreFlow, I'm setting a mock <URL>, say https://test.com.

And for example if I have conditional flows in the proxy, I set a target.url in their corresponding AssignMessagePolicy dynamically/statically based on the incoming request.

For eg.

<AssignMessage name="assignvariable-1">
  <AssignVariable>
    <Name>target.url</Name>
    <Value>https://mocktarget.apigee.net/echo</Value>
  </AssignVariable>
</AssignMessage>

OR

<AssignMessage name="assignvariable-1">
  <AssignVariable>
    <Name>target.url</Name>
    <Ref>request.queryparam.targeturl1</Ref>
  </AssignVariable>
</AssignMessage>

The target.url property may be set in an assignmessage policy or even in a javascriptPolicy in a TargetPreflow.

However, in the debug session, when I look at the CURL from "COPY CURL" option, the URL is displayed incorrectly , for eg:"curl -X GET 'https://test.com//'" and not the one set in target.url. The actual request is anyway sent to the one set in target.url as I'm seeing the response from the url set there in target.url.

Any workaround to see the actual cURL sent to the targetserver. Apigee Edge shows correct cURL but Apigee X doesn't.

0 1 76
1 REPLY 1

That seems like a bug!  Can you report this through the Apigee support team please?