Azure Function Proxy Cookie in Original Request Is Truncated When Routed to BackendUri

Tim Gulstine 1 Reputation point
2020-07-20T19:18:06.847+00:00

We are using proxies.json to set up proxies for some of our API requests (where the endpoints are Azure functions). However, when the request is routed to the backend uri, and the Azure function at the endpoint is executed, we see that the cookie has been truncated.

The cookie is a fairly long token (about 2K). It is stored in the original request header in the format:

Identity=[2K cookie]

But again, when we pull it from the HTTP Request while executing the Azure function (endpoint), we find that it has been truncated to a shorter length (approx 1600 bytes). Is there some reason why this might happen?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,522 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,240 questions
{count} votes