Kong
WebSocket requests not containing cookies or partial
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:
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.
Reproduction Steps
No response
Is there an existing issue for this?
- [x] I have searched the issue tracker for this problem.
Which sync method do you use?
- [ ] Git sync.
- [ ] Insomnia Cloud sync.
- [x] Local only
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
Same issue:
Version: Insomnia 10.3.1 Build date: 2/7/2025 OS: Darwin x64 24.1.0 Electron: 33.3.1 Node: 20.18.1 Node ABI: 130 V8: 13.0.245.24-electron.0 Architecture: x64
Having the same issue
works when adding API key to Header
doesn't work for Cookie
