We need to figure out how to make Juggernaut use secure connections. We've already packaged its Javascript in the app itself so that script tags don't use HTTP and cause unsecure content warnings, but the socket.io connection still uses plain HTTP.
In the meantime, it should be noted that user authentication information (such as a password) is never transmitted through Juggernaut.
Webkit browsers were ok with an HTTPS site connecting to a non-secure site using socket.io, but it turns out Firefox wasn't, so I fixed this ahead of schedule.
We need to figure out how to make Juggernaut use secure connections. We've already packaged its Javascript in the app itself so that script tags don't use HTTP and cause unsecure content warnings, but the socket.io connection still uses plain HTTP.
In the meantime, it should be noted that user authentication information (such as a password) is never transmitted through Juggernaut.