-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.AspNetCore.Server.Kestrel.Core throw when using Set-Cookie workaround #5661
Comments
@kepikoi - the workaround is a bit old, are you able to do this?
|
@mhoeger thank you, I am aware of this solution. Unfortunately this approach has its own limitations, which is it doesn't work via the |
@mhoeger can you please look it into this. |
@kepikoi , Apologies for the delay, Can you let us know if you were able to find a solution. Let us know if you require a follow up for this issue |
@v-anvari I haven't found a solution. AFAIK this is still an issue |
Thank you for the update, I shall follow up with the team |
Hi @alrod , Do you have any inputs here. |
This comment #2737 (comment) describes a workaround for setting multiple cookies in a HTTP triggered function. Unfortunatly it doesn't seem to work in azure-functions-core-tools
#Repro
Calling this function yields
Microsoft.AspNetCore.Server.Kestrel.Core: Invalid non-ASCII or control character in header: 0x0020
. The0x0020
bit probalby refers to the extra space character in theSet-Cookie
header. Here's an execution log from my local azure-functions-core-tools:Environment:
The text was updated successfully, but these errors were encountered: