The common solution suggested is to disable experimental feature NSURLSession WebSockets: NSURLSession WebSockets requests compression by including the Sec-WebSocket-Extensions: permessage-deflate header, but ignores when the server responds as not supporting it, and continues assuming the connection is compressed. NSURLSession WebSockets's inability to process split messages normally. So, based on the discussions in the above listed pages, there are two causes of websockets failure in Safari in macOS 12.2.1: With this exploration, following forums/threads had useful information on WebSockets issue related to Safari post macOS 12.2 upgrade: This gave a hint on to look for issues related to Safari and websockets specific to Monterey. Is closed before the connection is established. Based on the suggestion from Slack support team, analysing the Safari console output during the issue had following error related to websockets:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |