Revision history [back]

There could be several reasons why the Cookie header was not included in the inbound request (Trace) in Azure API, even though it was included in Postman:

1. The API may be configured not to accept cookies.

2. The API may be designed to strip out certain headers, including the Cookie header, for security reasons.

3. There may be a bug in the API that is causing the header to be dropped.

4. There may be an issue with the way Postman is sending the Cookie header, such as using an unsupported cookie format or encoding.

To troubleshoot the issue, you can try the following:

1. Double check the API documentation to make sure that cookies are supported.

2. Use a network traffic analyzer like Fiddler or Wireshark to see if the Cookie header is being sent by the client and if it is being received by the server.

3. Try sending the request using a different tool or library to see if the same issue occurs.

4. Contact the API provider for support.