You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be good to have the option to configure TLSClientConfig in Gorilla websocket. This would enable the utilization of unsigned certs which seems to be an impossibility right now for wss (?)
It could potentially be a setting in the Client struct, much like how Kite has TLSConfig for its listener. Or it could just inherit c.LocalKite.TLSConfig when c.dial initializes &sockjsclient.DialOptions.
In addition, a method of setting the TLSConfig for k.kontrol.Client would be useful as well.
I tried to implement this myself but I ran into some strange issues with heartbeat session authentication between a client and kontrol.
The text was updated successfully, but these errors were encountered:
I think it would be good to have the option to configure TLSClientConfig in Gorilla websocket. This would enable the utilization of unsigned certs which seems to be an impossibility right now for wss (?)
http://godoc.org/github.com/gorilla/websocket#Dialer
It could potentially be a setting in the Client struct, much like how Kite has TLSConfig for its listener. Or it could just inherit c.LocalKite.TLSConfig when c.dial initializes &sockjsclient.DialOptions.
In addition, a method of setting the TLSConfig for k.kontrol.Client would be useful as well.
I tried to implement this myself but I ran into some strange issues with heartbeat session authentication between a client and kontrol.
The text was updated successfully, but these errors were encountered: