You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.
So it turns out that Socket.io uses a secure websockets connection if the connection is over HTTPS, which should have been obvious. Still, I wonder if the issue referenced in issue 6 is related to the server using the wrong SSL certificate. If so, I should find a way to specify a particular certificate.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Making a note to myself that I should add the ability to force HTTPS connections if there is a compatible SSL certificate.
The text was updated successfully, but these errors were encountered: