You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using request.headers.get("cookie") on https I get a string that uses commas instead of semicolons as delimiters, even though the cookie in the Header in browser clearly has semicolons as delimiters.
I can repro this on windows with --useHttps. Interestingly, the problem seems to go away if you use the preview http streaming feature.
app.setup({enableHttpStream: true});
I'm pretty sure our node.js logic is just passing along the headers we get from the host, so this one might have to be addressed in the host
Possibly related to Azure/azure-functions-host#4486 and/or dotnet/runtime#42856. Note it's confusing because "Set-Cookie" is supposed to use a comma as a delimiter but "Cookie" is supposed to use a semicolon.
When using
request.headers.get("cookie")
on https I get a string that uses commas instead of semicolons as delimiters, even though the cookie in the Header in browser clearly has semicolons as delimiters.Example: https://github.com/pellebjerkestrand/azure-functions-core-tools-https-cookie-commas
The expected behavior is for the delimiter to be the same as in the browser.
The text was updated successfully, but these errors were encountered: