Android Chrome websocket error (net::ERR_TUNNEL_CONNECTION_FAILED)

[steven winner]

I'm running Cometd 3.0.3, and have websockets setup using JettyWebSocketTransport (not the JSR 356 websocket transport).  Everything works great on the desktop browsers, but testing out mobile browsers on my Android (Samsung Note 3, 4.4.2), Firefox connects via websockets, but Chrome (39.0.2171.93) gives this error and falls back to using long-polling:

WebSocket connection to 'ws://mycometdserver.com/rt/serve' failed: Error in connection establishment: net::ERR_TUNNEL_CONNECTION_FAILED

the native samsung browser doesn't use websockets either, but I know that some iterations of their browser still haven't implemented websockets fully yet, but I'm trying to figure out why Chrome isn't connecting successfully via websockets, or if anyone else is seeing this.  I have the latest version of the cometd.js library as well, so that shouldn't be it.

Thoughts?

[Simone Bordet]

Hi,

The URI shows a scheme of "ws" which would indicate clear-text connection.
The error "ERR_TUNNEL_CONNECTION_FAILED" is instead typically
happening when using SSL.

I am guessing you have some misconfiguration in your setup with regard
to URI schemes (use "https" rather than "http" for your CometD URIs),
or perhaps you're using a proxy, or something like that.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.