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
and we can see that there is no response from the server
I have found out that by changing the transports to 'polling' insted of 'websocket' let the browser connect to the server, but I still rather use websocket insted of long polling.
I am using engine.io-server 6.0.1 and Java 17.
the error occured on chrome and edge, didnt check different browsers.
The text was updated successfully, but these errors were encountered:
After Debugging, I have found the issue is not related to this library, but rather its a problem laying in spring.
I have the problem is caused because the browser Origin HTTP Header, which the node.js application one doesn't have.
the OriginHandshakeInterceptor.beforeHandshake() treat the origin header, even if its null as a String ("null"), therefore it fails all the checks and the connection is dropped.
I have found a quickfix, but I am no expert to determine if its a good one.
Hey, I have followed the guide on https://github.com/socketio/engine.io-server-java/blob/master/docs/spring-integration.rst
and have succsfully connected engine.io socket using Node.js application with the following code.
Bean
Node.js Code
but the same code just for the browser doesnt work.
Browser Code
and we can see that there is no response from the server
I have found out that by changing the transports to 'polling' insted of 'websocket' let the browser connect to the server, but I still rather use websocket insted of long polling.
I am using engine.io-server 6.0.1 and Java 17.
the error occured on chrome and edge, didnt check different browsers.
The text was updated successfully, but these errors were encountered: