-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work over HTTPS (on Heroku) #7
Comments
Good point, I'll fix that asap! |
Fixed: 5afd9c9 |
Thanks! Have you published the fix to NPM? |
I've just pushed version |
Cheers mate! |
Just checked the latest version - doesn't work. If I browse to my web site without specifying http/https in the address page, and then add the '/status' route, I get |
^^ experiencing this issue as well. Firewall is open, but my SSL cert doesn't like this being in http |
Please reopen the issue. It still occurs. I suspect it may have something to do with the port number, and the way it's specified. |
Sorry for that, I'll try to fix that. |
Thank you guys for your input and fast reaction! Version You can test https support here: https://safe-fjord-78017.herokuapp.com/status |
Just added the route to an Express app I have deployed to Heroku and I'm getting the following error (repeated every second):
Can you maybe provide a way to specify whether the Socket.io call be made over HTTPS, or better yet, handle this automatically?
The text was updated successfully, but these errors were encountered: