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
Darwin MBP.local 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
When specifying multiple Cookie headers for a fetch request, the headers will be concatenated using commas instead of semicolons. While this is technically compliant with the WHATWG spec, that spec is based around browser use and causes a risk of incorrect handling by the receiving server.
Version
19.6.0
Platform
Darwin MBP.local 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
When specifying multiple
Cookie
headers for a fetch request, the headers will be concatenated using commas instead of semicolons. While this is technically compliant with the WHATWG spec, that spec is based around browser use and causes a risk of incorrect handling by the receiving server.Example:
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
Cookies are separated by semicolons (
;
).What do you see instead?
Cookies are separated by commas (
,
).Additional information
Similar issue but on the receiving end: nodejs/node#11256
The text was updated successfully, but these errors were encountered: