#1211 closed defect (fixed)
websockify and named pipe timeouts on win32
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 1.0 |
Component: | platforms | Version: | trunk |
Keywords: | win32 websockify | Cc: |
Description
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.
Attachments (2)
Change History (6)
Changed 6 years ago by
Attachment: | html5-win32.patch added |
---|
comment:2 Changed 6 years ago by
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.
comment:3 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
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)
comment:4 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1211
try to use blocking socket everywhere and wrap win32 non-blocking socket calls