-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix(client): dynamic protocol for socket.io #1401
Conversation
@clexit Thanks! Are you use https proxy? |
Hi @maksimr! Yes, it's https that proxies to the local Karma instance. Since there is only https, socket.io fails to connect because of the hardcoded protocol (it tries to connect from https to the nonexistent http). While local http Karma is ok, we cannot configure http proxy due to security restrictions. Can this change be merged? I've just noticed that the tag in the commit message might be incorrect. Does it matter for merge? |
@clexit
Yes, I think it's good change!
What tag? cli? I think will be better change scope to
Thanks |
Look up location.protocol for socket.io, in order to use Karma in https-only enviournment Closes #1400
Cool, thanks! I changed the scope tag to |
@clexit Thanks LGTM |
LGTM |
#merge |
Sent to presubmit as presubmit-master-pr-1401 |
#merge |
#merge |
Sent to presubmit as presubmit-master-pr-1401 |
#merge |
Sent to presubmit as presubmit-master-pr-1401 |
fix(client): dynamic protocol for socket.io
Look up location.protocol for socket.io,
in order to use Karma in https-only enviournment
Closes #1400