Service Callouts are breaking?

Google Cloud Apigee
1

Hello There,

We have got two service callout policy executing consequently. Suddenly the second service callout, which was working earlier, started failing and giving unexpected result.

After investing a lot of time, I realized that Apigee has started adding attributes clearPayload=“false” variable=“servicecallout.request” to the Request object, which appends the request uri of the service callout to the second service callout’s request uri.

For example:

First service callout : https://example.com/developer

Second service callout: https://example.com/apps

What’s now happening is second service callout url becomes https://example.com/apps/developer and it leads to service callout getting failed.

Is it a new bug that Apigee has introduced or have they fixed an existing bug and expect this to be a behaviour? If they have fixed the bug why developers were not notified.

Thanks

2

If you are facing the similar issue, please add the attribute variable to the request object with a value other than servicecallout.request.

For example: