-
Updated
Apr 27, 2022 - Go
socket
Here are 4,595 public repositories matching this topic...
-
Updated
May 12, 2022 - PHP
Which version are you referring to
3.1dev
We list not all RFCs in ~/doc/ which we refer to in testssl.sh.
List used RFCs: grep RFC -w ./testssl.sh | grep -v TLS_CIPHER | grep RFC | sed 's/^.*RFC/RFC/' | sort -u
List RFCs referred to: grep -w RFC doc/testssl.1
-
Updated
Jan 31, 2022 - Objective-C
-
Updated
Nov 16, 2021 - Go
-
Updated
May 8, 2022 - JavaScript
-
Updated
Oct 31, 2021 - TypeScript
-
Updated
Jan 10, 2020 - Java
-
Updated
Mar 23, 2022 - Go
-
Updated
Feb 24, 2017 - Java
-
Updated
Sep 26, 2021 - Java
-
Updated
Oct 4, 2021 - Swift
-
Updated
Jan 16, 2019 - Objective-C
-
Updated
Feb 7, 2019 - C#
-
Updated
Apr 19, 2022 - PHP
-
Updated
Sep 12, 2021 - C#
-
Updated
May 10, 2020 - Java
Hi,
I am trying to figure out how to test the server side. I am using mocha, chai and sinon but really don't know how to emulate a websocket client on the server side so that I can test its flow. Could you help or suggest what client to use to initiate connect from the test?
Thank you.
Kind regards,
Jarek
Improve this page
Add a description, image, and links to the socket topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the socket topic, visit your repo's landing page and select "manage topics."
Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef