Untrusted Secure Websocket broken on latest chrome dev

[Carreau]

Hi,
IPython websocket seem to be broken on last chrome dev (19.0.1068.0 dev, [march 13 I think]), jQuery pop up at startup :

Websocket connection to wss://localhost:8888/kernels/dff85e51-da2a-49c9-915a-6b93b5d8e3e7
could not be established. You will NOT be able to run code. Your browser may not be compatible
with the websocket version in the server, or if the url does not look right, there could be an
error in the server's configuration.

Nothing in js console

Wherease some websocket testing site like http://websocket.org/echo.html works.
Does anyone have the same probleme ? I rolled back to chrome stable and it works fine.

last commit of master: 3912ea7 , https with password, on mac.

[takluyver]

Can you test without https, to see if it's only an issue with secure websockets?

[Carreau]

Yes, I can, and yes it works.

[minrk]

Is your certificate trusted? It could be that Chrome is giving up on the websocket connection with an untrusted certificate.

Or, as has been true in the past with a couple ws issues, it's just a Chrome bug and will be fixed shortly.

[minrk]

After testing with a trusted certificate, I'm pretty sure this is the case. Chrome is refusing to establish wss connections with untrusted certificates. I'm not sure how to get a certificates to be trusted on localhost, because Chrome is giving me:

The identity of this website has not been verified.

The identity of the server you are connected to cannot be fully validated.

Even though I've instructed my system to trust the certificate. When I use a trusted certificate for non-localhost address, then wss connections work fine.

[Carreau]

ok, good to know, i'll try to look at it again on tuesday.
Thanks.

[jeffhsu3]

I'm getting a similar issue, but only when using ipython notebook within a virtual environment.

[Carreau]

well , seem to be fixed on (19.0.1084.1 dev) as of today april 2cnd.
Closing then...