-
Notifications
You must be signed in to change notification settings - Fork 51
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
EngineIO Client could not keep connection alive when using SSL #16
Comments
My further investigation below.
|
The status code 503 is |
Also, I don't know what browser you're using but https to localhost seems troublesome and could be the thing causing the issue. EDIT: Please make sure you're using a certificate that your browser trusts. This could be the issue causing the |
@trinopoty I can ensure the server is available, and from the logs, you can see that the first connection has been established because the client received a message from server I used the engine-client in node. I will try to config the ssl options. Thanks for your quick reply! |
It seems the error caused by the server since I tried a simple demo and it connected successfully. |
I see. Thanks for the update. |
I have found the root cause, it's caused by |
Hi,
I tried to connect an SSL engine-io server but got failed.
Server Code
The following is my server code, I deploy the servlet in a
Jetty Container
which is using SSL.maven dependency
Client Code
I created an engine-io client using engine.io-client.
dependency
Errors
When I executed the client code using
node client.js
, it showed the first connection has been established, but the connection couldn't keep alive.The text was updated successfully, but these errors were encountered: