This project is read-only.

forced certificate validation with websocket

Jun 10, 2014 at 11:24 AM
I noticed that even if ServerCertificateValidationCallback is used to validate any certificate it will not work for websocket as it uses it's own switch.
It would be good to be able to access this:
this.wsClient.AllowUnstrustedCertificate
from Client api.

Or is there any way do do it already?
Coordinator
Jun 11, 2014 at 1:03 AM
Edited Jun 11, 2014 at 3:28 AM
By chance - are you running into something similar to http://stackoverflow.com/questions/14601832/can-not-connect-to-websocket-server-using-websocket4net

If so, setting via the ctor may help in the short term

Client(string url, WebSocketVersion socketVersion)

Otherwise, I'd suggest heading over to https://github.com/jstott/socketio4net/tree/develop, please add the issue there and or a pull requests if you have something already.

Jim
Jun 11, 2014 at 7:11 AM
The scenario is that I have a client connecting to self-signed websocket server.
As this is development phase I temporary modified the Client.cs code to allow this.
Thus there is no problem, it would simply be easier if the code was ready for handling this via api.
Coordinator
Jun 11, 2014 at 12:44 PM
Thank you for the suggestion, will target for future enhancements.