Xpra: Ticket #1681: allow http/websocket over unix socket when --html

xpra supports binding to unix sockets.

At first it doesn't sound like HTTP over Unix socket would be useful, because browsers can't connect to unix sockets. However:

ssh supports proxying unix sockets to IP ports elsewhere.

This can be useful because it can keep other Unix users on the box running xpra server from trying to connect to xpra.

When I combine --bind= and --html=on, however, the browser receives "this port does not support HTTP requests", and xpra logs "Error: unix-domain connection failed"..."invalid packet header, HTTP GET request".

Are there reasons not to change xpra to allow HTTP on unix socket when --html is on?

Sat, 11 Nov 2017 17:07:14 GMT - Antoine Martin: owner, component changed

owner changed from Antoine Martin to idupree

component changed from html5 to network

Turned out to be (almost) trivial, so done in r17381.

Tested with:

server:

xpra start --start=xterm  --daemon=no -d network,websocket :10

socat to make the unix-domain socket available as TCP:

socat TCP-LISTEN:20000,fork  UNIX:$XDG_RUNTIME_DIR/xpra/$HOSTNAME-10

point browser at the TCP port:

xdg-open http://localhost:20000/

@idupree: please close if that works for you.

Fri, 24 Nov 2017 16:06:48 GMT - Antoine Martin: status changed; resolution set

status changed from new to closed

resolution set to worksforme

Sat, 23 Jan 2021 05:30:56 GMT - migration script: