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
This is hard because in a lot of cases, we process socket upgrades to SSL without knowing if the socket is going to be:
a websocket connection
an https client
a plain ssl connection
And each one of these can have its own toggle.
But it is needed because we currently assume too much. For example, we publish mdns records based on generic socket type mappings rather than what we end up using for deciding whether to upgrade a socket or not.
Currently the server will not "upgrade" sockets unless the html5 client is installed (the
_html
flag):xpra/xpra/server/server_core.py
Line 1549 in aa1e864
Technically, there is no reason for this:
etc
The current workaround is to add
http=true
(orhttps=true
for ssl) to the socket options, ie:--bind-tcp=0.0.0.0:10000,http=true
The text was updated successfully, but these errors were encountered: