Received: by 10.236.190.68 with SMTP id d44mr35114286yhn.1.1329777728091;
        Mon, 20 Feb 2012 14:42:08 -0800 (PST)
X-BeenThere: socket_io@googlegroups.com
Received: by 10.101.168.4 with SMTP id v4ls3603312ano.6.gmail; Mon, 20 Feb
 2012 14:42:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.236.176.6 with SMTP id a6mr2551397yhm.12.1329777723253; Mon,
 20 Feb 2012 14:42:03 -0800 (PST)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 jeffzimmer...@gmail.com designates internal as permitted sender)
 smtp.mail=jeffzimmer...@gmail.com; dkim=pass
 header...@gmail.com
Received: by f2g2000yqh.googlegroups.com with HTTP; Mon, 20 Feb 2012 14:42:03
 -0800 (PST)
Date: Mon, 20 Feb 2012 14:42:03 -0800 (PST)
In-Reply-To: <4F4296E8.80009@eserre.com>
References: <3361ab94-13e5-4449-9569-abde2bb4bd4f@t24g2000yqj.googlegroups.com>
 <4F4296E8.80009@eserre.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3)
 AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11,gzip(gfe)
Message-ID: <3babcf50-ff40-48f9-b05a-be38727a3014@f2g2000yqh.googlegroups.com>
Subject: Re: Node.js + Socket.IO + SSL = Not Working on Leopard (10.5 -
 10.5.8) Clients
From: Jeff <jeffzimmer...@gmail.com>
To: "Socket.IO" <socket_io@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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...

On Feb 20, 10:54=A0am, Jose Luis Rivas <josel...@eserre.com> wrote:
> On 02/20/2012 01:15 PM, Jeff wrote:
>
>
>
>
>
>
>
> > Hey everyone,
> > I have a Node.js + Socket.IO web app. =A0I 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?
>
> 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/