Xpra: Ticket #1211: websockify and named pipe timeouts on win32

For some unknown reason, sockets refuse to go into blocking mode on win32, causing all sorts of problems. The patch attached tries to workaround this issue by wrapping the send and recv methods, but still fails to allow win32 to use websockify reliably as the http server code calls socket.sendall from its flush function, and this cannot be overriden.

Sun, 29 May 2016 06:49:35 GMT - Antoine Martin: attachment set

try to use blocking socket everywhere and wrap win32 non-blocking socket calls

Tue, 12 Jul 2016 16:52:22 GMT - Antoine Martin: milestone changed

Milestone renamed

Mon, 15 Aug 2016 06:41:11 GMT - Antoine Martin: attachment set

allow websockify to run on win32

Mon, 15 Aug 2016 09:00:58 GMT - Antoine Martin:

As of r13352 (+ minor fixup in r13355), we can use the websockify html5 server on win32. Websockify still needs the attachment/ticket/1211/websockify-win32.patch, which I will try to upstream, at least in part.

Sun, 25 Sep 2016 15:59:08 GMT - Antoine Martin: status changed; resolution set

Some related changes in ticket:1298#comment:3, websockify re-fixed on win32 in r13866 + r13867: use a high timeout for http (high enough that we have time to service requests), only apply the socket workaround for websockify traffic.

Play platform bug whackamole for a few more hours: r13870 + r13872: I can now connect with the html5 client to all servers, including shadow servers on win32 and osx, and including through the proxy (made easier by the new username and password fields: r13869 + r13873)

Sat, 23 Jan 2021 05:18:01 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1211