Node.js + Socket.IO + SSL = Not Working on Leopard (10.5 - 10.5.8) Clients

[Jeff]

Hey everyone,
I have a Node.js + Socket.IO web app. I just rolled out SSL support
about a week or so ago, and in the last few days, started forcing all
of my clients to use it.

Everything has been going great, except some of my clients using older
versions of Mac OS X Leopard (10.5 - 10.5.8) are getting "Uncaught
ReferenceError: Socket is not defined" and "Uncaught ReferenceError:
io is not defined" errors.

Their user agent strings were:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.11
(KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:9.0.1) Gecko/20100101
Firefox/9.0.1

SSL works beautifully for everyone else.

Any idea what might cause this?

[Jose Luis Rivas]

If your socket.io client-side js is in a different document, then maybe
those browsers do not accept loading documents from URIs not
SSL-protected. There are browser settings that allow this kind of stuff
for security measures.

If that's the case you just need to make all requests SSL.

--
Jose Luis Rivas, Web Builder
Eserre -- http://www.eserre.com/
Venezuela - GPGs: 7C4DF50D B9AC8C43

[Jeff]

Everything is encrypted using SSL, from the HTML served, to the
Node.js/Socket.IO chatter, to the socket.io.js file served.

Any other ideas? It's odd that it only affects Leopard users...

> Eserre --http://www.eserre.com/

[Ryan Gahl]

We ran into a few glitches like this recently, and the solution was
(for us anyway) that you need to make damn sure your TLS options for
the socket.io shim https server are exactly the same as your main
https server instance. In our case, we had missed the CAs in the
socket.io shim. Different browsers have different levels of strictness
about this (most others were fine to allow the slightly-less-verified
cert). Once we made sure the CAs were properly applied to both https
servers (i.e. TLS options match exactly), stuff was happy again.

[Jeff]

That's totally it! Thank you!

For others with a similar problem, I got my SSL certificate from
Namecheap (PositiveSSL/Comodo) and my code looked like this:

HTTPS_Options={
key: FS.readFileSync('/path/to/.key'),
cert: FS.readFileSync('/path/to.crt')
};

but should have looked like this:

HTTPS_Options={
key: FS.readFileSync('/path/to/.key'),
cert: FS.readFileSync('/path/to.crt'),
ca: FS.readFileSync('/path/to.ca-bundle')
};

Adding the .ca-bundle file fixed the issue.

Thanks!