On 03/05/2022 14:12, Hagenauer, Florian wrote:
<snip/>
Does anyone have an idea or is able to clarify if this is an issue with Tomcat
or with Safari/WebKit? Or if there is a workaround to this issue?
I've just run Safari on a fully updated macOS Monterey against the
Autobahn|Testsuite for the WebSocket protocol.
Safari failed multiple tests, mostly in the compression sections. Safari
also exhibited multiple "non-strict" results which indicate things like
closing a connection with the wrong close code.
Tomcat fully passes the Autobahn|Testsuite.
Given the above, it seems reasonable to conclude that there are still a
few bugs in Safari's WebSocket implementation that need fixing.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
