Skip to content
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

Failed to connect Spring Boot 1.4.2 (Tomcat 8.5.6) #30

Open
VelniasGriebtu opened this issue Dec 11, 2016 · 4 comments
Open

Failed to connect Spring Boot 1.4.2 (Tomcat 8.5.6) #30

VelniasGriebtu opened this issue Dec 11, 2016 · 4 comments

Comments

@VelniasGriebtu
Copy link

I'm trying connect to Spring Boot server (v1.4.2, Tomcat 8.5.6) valid CA signed certificate (SHA256withRSA, SHA1withRSA, 2048) and GOT ALERT! type=40, which looks like handshake issue. Any insight is appreciated.

@VelniasGriebtu
Copy link
Author

The connection issue was solved by configuring property server.ssl.ciphers=ALL.
Now I get protocol errors on server side. It happens when fragmented message is sent by the client. E.g.
CloseStatus[code=1002, reason=A WebSocket frame was sent with an unrecognised opCode of [15]];
CloseStatus[code=1002, reason=The client frame set the reserved bits to [6] for a message with opCode [15] which was not supported by this end

@neminovno
Copy link

Maybe Explanation helps?

@VelniasGriebtu
Copy link
Author

The issue above occurs on IE 11.0 and works fine under Chrome.

@VelniasGriebtu
Copy link
Author

I tried set origin other than '', e.g.
new WebSocket("ws://localhost:4321/", "http://localhost:4321/");
It works only if you set allowed origins as '
' on the server side. Otherwise you get 403.
When I request the same server from JS - it works fine with same origin server policy or 'http://localhost:4321/ allowed'.
Any idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants