Open MayamaTakeshi opened 3 years ago
One alternative is to send the access token back in the login info and use it in the ws request:
Started GET "/cable?access_key=f7f443c20f7d48f8d9dbec06f716a15a0e275eec" for 192.168.181.113 at 2021-08-09 14:24:04 +0900
Started GET "/cable/?access_key=f7f443c20f7d48f8d9dbec06f716a15a0e275eec" [WebSocket] for 192.168.181.113 at 2021-08-09 14:24:04 +0900
Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
Token Load (1.0ms) SELECT `tokens`.* FROM `tokens` WHERE `tokens`.`action` = 'api' AND `tokens`.`value` = 'f7f443c20f7d48f8d9dbec06f716a15a0e275eec' LIMIT 1
User Load (0.7ms) SELECT `users`.* FROM `users` WHERE `users`.`type` IN ('User', 'AnonymousUser') AND `users`.`id` = 1 LIMIT 1
Registered connection (Z2lkOi8vcmVkbWluZS1hcHAvVXNlci8x)
RedmineRt::Channel is transmitting the subscription confirmation
RedmineRt::Channel is streaming from user:admin
RedmineRt::Channel is transmitting the subscription confirmation
RedmineRt::Channel is streaming from general
After updating chrome to latest version, this webextension stopped working.
The problem is that chrome is not sending the Cookie in WebSocket request anymore.
Here are for comparison with firefox the relevant messages:
Firefox 90.0.2 (OK):
Chrome 92.0.4515.131 (NG: No Session Cookie):