Steps to reproduce: 1. Create new web extension 2. Visit some domain you control to have it's cookies in the Browser 2. On the background page of the extension, try to create new secure websocket connection to the same domain (wss://, backend must be able to handle socket connections, of course) Expected outcome: Connection established, cookies for domain are sent with it, backend is able to read them Real outcome: Connection established, cookies for domain are not visible from the backend, as if they were not sent Additional information: Developer Tools show what cookies are being sent and recieved from backend during connection, but backend can't see them. Looks like they are lost somewhere during connection
<rdar://problem/83468404>