When Firefox starts a WebSocket client handshake, no Cookie header is sent to the WebSocket server, even if cookies are set for the domain. This may be on purpose for same-origin (page is on port 80 and websocket server is port 3000), but on other browsers the Cookie header is sent to the server.
need a specific STR (steps to reproduce) to determine what the appropriate behavior should be.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.