Announcements
The Google Cloud Community will be in read-only from July 16 - July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Trace displays curly braces even after the variable's value is replaced

I have created a proxy where I am using different conditional flows. Each of the flows require different target URL. So, I have used assign message policy for each of the conditional flow to store the path value in a variable in the ProxyEndpoint, like this (I know that we can do this using JS policy at TargetEndpoint as well but just gave this a try!):

<AssignVariable>  
<Name>url</Name>  
<Value>authentication/oauth</Value>  
</AssignVariable>

Then I access this variable in the TargetEndpoint like this:

<HTTPTargetConnection> 
<Properties/>  
<URL>https://sample.com:4567/{url}</URL>  
</HTTPTargetConnection>

When I execute the proxy, the call is successful but when I have a look at the 'Request sent to target server' in trace, I can see that the variable is still present with curly braces along with the replaced value.

4939-ass-var.jpg

Does anyone have any idea as to why the trace still shows the variable within curly braces ({url})along with the replaced value of the variable?

1 8 626
8 REPLIES 8