[Webkit-unassigned] [Bug 149551] [SOUP] Slack.com is not working, new messages do not load due to WebSocket authentication failure issue

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Sep 25 06:59:13 PDT 2020


https://bugs.webkit.org/show_bug.cgi?id=149551

Carlos Garcia Campos <cgarcia at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pgriffis at igalia.com

--- Comment #26 from Carlos Garcia Campos <cgarcia at igalia.com> ---
I've found the problem, but not the solution yet, maybe Patrick can help. The problem is that we are not including all the cookies in the web socket request. There are two cookies with the Lax same-site policy set, that are not included for the websocket request because it's not considered a top site navigation and the hosts don't match (app.slack.com - wss-primary.slack.com). I don't know how same-site cookies work, so I don't know if we need to make an exception for websockets or consider them a top site navigation. Maybe it's a WebKit bug that should mark the websocket request as same site? Patrick?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200925/b9242090/attachment.htm>


More information about the webkit-unassigned mailing list