Weird Problem : with Set Cookie Header

Google Cloud Apigee
1

When making a call to backend API from postman, the response header contains

Set-Cookie JSESSIONID=xxa0R_yOx6ZVShMs5Oyw;

However when Apigee proxy makes a call to the same backend API with exact same header & payload we get

Set-Cookie JSESSIONID=_shared_session_1234

Has anyone seen this kind of behavior and its cause ? Thanks in advance.

2

when Apigee proxy makes a call to the same backend API with exact same header & payload we get

When you say “we get”, how are you determining this? Where are you “getting” the header? Are you observing this at the client, or … in the Apigee Edge trace? or…somewhere else?

What does your API Proxy do? Does it modify the header explicitly, in the response flow?