Apigee caches target.url for a Proxy from the previous request. Is it a bug?

[BoyWonderSAM]

As part of an API the developer forgot to set the target.url but has LoadBalancer configuration at the target endpoint.

Also he has a code that checks if the target.url variable is not null then he adds a suffix to it as part of the javascript file.

While debugging I can see that the target.url is null the first time and the request goes to load balancer.

However, on the 2nd request, the target.url is populated and the suffix gets added. This keeps on going for the subsequent requests and the suffix keeps adding.

I undeployed and redeployed the API and target.url again started from null, load balance URL, and kept appending the suffix to the previous URL. Is it a bug?

Apigee OPDK Version 4.50.00

[BoyWonderSAM · Accepted solution]

 I did some testing with Edge and ApigeeX and it is not there. It looks like a bug in Apigee OPDK 4.50.00