Safari Error when connecting Websockets

[billyyarosh]

Safari 5.1.5 on Tomcat 7.0.27 In atmosphere jquery I get an error with "Unexpected response code: 202".

When tracing through the script I can't seem to tell why this is happening.

Invoking executeWebSocket
jquery-atmosphere.js:848Using URL: wss://localhost:8445/testing/subscribe/?X-Atmosphere-tracking-id=a5fb7b57-deec-b7c3-f196-5c8c0cd4f243&X-Atmosphere-Framework=0.9&X-Atmosphere-Transport=websocket&X-Cache-Date=0
:8445Unexpected response code: 202
jquery-atmosphere.js:848Websocket closed, reason: undefined
jquery-atmosphere.js:848Websocket closed, wasClean: false
jquery-atmosphere.js:848Invoking request callbacks
search:227response.responseBody is null - ignoring.

[billyyarosh]

It seems to me that Safari's Websockets implementation is not liking the response code sent back from Tomcat. This doesn't make sense, though since a 202 would seem proper for an async request.

[jfarcand]

It has been fixed to a 501 yesterday :-)

  https://github.com/Atmosphere/atmosphere/issues/324

Your javascript should just catch that and reconnect using the fallback transport. Thanks as usual!

[billyyarosh]

So is websockets support unavailable in Safari?

[billyyarosh]

Or is Safari and Tomcat not workable

[jfarcand]

Tomcat WebSocket's implementation doesn't support the old Safari WebSocket implementation, unfortunalty.

[billyyarosh]

The old Safari WebSocket implementation? Does this mean that Safari has a future release that Tomcat will support?

[jfarcand]

Safari 5.1 supports an old version of the WebSocket Spec. Once Safari support a newer version the current Tomcat will supports it.

[billyyarosh]

Ok that makes sense. Thanks.