search

asleepysamurai / socketwrench

Quick and Easy Websocket Testing.
114 stars 3 forks source link

WSS issue #13

Open hunterdishner opened 4 years ago

hunterdishner commented 4 years ago

I'm honestly not sure what's wrong but I've created a golang server that uses TLS and am having a terrible time getting the app to connect. I've used a few different web-socket tools through Chrome and they all will connect to the server just fine. If I disable TLS and just use the "ws" address then everything works though. Unfortunately I can't find the error logs to be of more help or I would definitely post them.

Is there something I could try or somewhere I could look to see what the issue might be? I need the ability to send an API key through to the initial connect and only socket wrench has had the ability to specify headers. All the rest I've tried have not been capable of it.

asleepysamurai commented 4 years ago

Ah, sorry about that. Socket wrench does not support tls at the moment. It's been on the list of requested features for a while now, but I've been a bit busy with other things to focus much on it.

I do have some time coming up in the next few weeks and I intend to work on it, but I cannot give any guarantees at the moment.

On Sun, Jul 26, 2020, 15:11 Hunter Dishner notifications@github.com wrote:

I'm honestly not sure what's wrong but I've created a golang server that uses TLS and am having a terrible time getting the app to connect. I've used a few different web-socket tools through Chrome and they all will connect to the server just fine. If I disable TLS and just use the "ws" address then everything works though. Unfortunately I can't find the error logs to be of more help or I would definitely post them.

Is there something I could try or somewhere I could look to see what the issue might be? I need the ability to send an API key through to the initial connect and only socket wrench has had the ability to specify headers. All the rest I've tried have not been capable of it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/asleepysamurai/socketwrench/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEND4JRNTY5NNE62RCQ3ULR5QTR3ANCNFSM4PH7GF2Q .

hunterdishner commented 4 years ago

Sounds good. I'm also testing the application with two windows open connecting to the same server. If I connect with a URL as such conversation/connect/38 and then try to connect in the second window with conversation/connect/44 then my server is receiving the 38 a second time. It seems that it's reusing the server / connection URL instead of just establishing an entirely new connection. I tried adding in a second server in the list on the left and trying it that way but it fails to connect when using a second "server" listing. I'm not sure if this is a limitation of something networking related in the OS or if the application is just accidently reusing the same connection / connection URL.

hunterdishner commented 4 years ago

Also will add I'm using it on macOS Catalina Version 10.15.16