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
One issue I have always had with WebSockets has been requests not sending cookies, or sending only 1 cookie.
In my case, a backend hosted on 127.0.0.1, the cookie header looks like this:
cookie: null;
However, that very same backend hosted on an external domain the cookie header will only send 1 cookie, and forgets about the rest of the cookies that match the cookie path:
cookie: a=1;
In the browser both scenarios work fine and 2 cookies are always sent reliably.
Actual Behavior
Sending null as a cookie value, or only sending 1 cookie, depending on the hostname.
Expected Behavior
One issue I have always had with WebSockets has been requests not sending cookies, or sending only 1 cookie.
In my case, a backend hosted on 127.0.0.1, the cookie header looks like this:
However, that very same backend hosted on an external domain the cookie header will only send 1 cookie, and forgets about the rest of the cookies that match the cookie path:
In the browser both scenarios work fine and 2 cookies are always sent reliably.
Actual Behavior
Sending
null
as a cookie value, or only sending 1 cookie, depending on the hostname.Reproduction Steps
No response
Is there an existing issue for this?
Which sync method do you use?
Additional Information
No response
Insomnia Version
10.3.1
What operating system are you using?
Windows
Operating System Version
Windows 11 Home Version - Windows Feature Experience Pack 1000.26100.48.0
Installation method
insomnia.com
Last Known Working Insomnia version
No response
The text was updated successfully, but these errors were encountered: