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
Websockets does support https. The client dialers expect you to pass scheme wss://, not https://.
That being said, the behavior your mentioning IMO is an issue (so picky about scheme), but bottom line is that gorilla websocket does support TLS and will connect to an https server.
It looks like gorilla websocket intends to support https, e.g logic here.
However, https is not registered during init here.
This caused https to be considered as an unknown proxy when we use https proxy, error thrown from here.
Is this a bug? Shouldn't the
proxy_RegisterDialerType
be initialized withhttps
?The text was updated successfully, but these errors were encountered: