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?
Turned out to be (almost) trivial, so done in r17381.
xpra start --start=xterm --daemon=no -d network,websocket :10
socat TCP-LISTEN:20000,fork UNIX:$XDG_RUNTIME_DIR/xpra/$HOSTNAME-10
@idupree: please close if that works for you.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1681