Skip to content
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.

tls 1.2 issue (browser side times out) #49

Open
softreigns opened this issue Nov 9, 2018 · 0 comments
Open

tls 1.2 issue (browser side times out) #49

softreigns opened this issue Nov 9, 2018 · 0 comments

Comments

@softreigns
Copy link

I am using the tls12 in the configuration and the supersocket server starts fine and performance collector is showing fine too.
The browser connects fine when I am using just "tls" in the security.

When I am connecting to the browser with server running in "tls12" mode, the server shows that the connection has opened and the collector also shows the connection.

2018-11-09 11:43:47,365 [7] INFO SecureSuperWebSocket - Session: 879cc16b-32cf-4b5c-83e8-18798e46ae36/127.0.0.1:58335
A new session connected!
2018-11-09 11:43:48,591 [6] INFO Performance - ---------------------------------------------------
CPU Usage: 1.93%, Physical Memory Usage: 45,481,984.00, Total Thread Count: 21
AvailableWorkingThreads: 32766, AvailableCompletionPortThreads: 1000
MaxWorkingThreads: 32767, MaxCompletionPortThreads: 1000
SecureSuperWebSocket ----------------------------------
Started Time: 11/9/2018 11:42:19 AM
Is Running: True
Total Connections: 1
Maximum Allowed Connection Number: 100
Total Handled Requests: 0
Request Handling Speed (#/second): 0
Avialable Sending Queue Items: 255
Total Sending Queue Items: 256

But on the browser side, in few sec the connection errors out
WebSocket connection to 'wss://server' failed: WebSocket opening handshake timed out

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

No branches or pull requests

1 participant