#2424 closed enhancement (fixed)
per socket options
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 4.0 |
Component: | network | Version: | 3.0.x |
Keywords: | Cc: |
Change History (6)
comment:1 Changed 19 months ago by
Status: | new → assigned |
---|
comment:2 Changed 19 months ago by
r23904 makes it possible to disable mdns on a per-socket basis, ie:
xpra start --no-daemon --bind-tcp=0.0.0.0:10000,mdns=no --bind-tcp=0.0.0.0:10001,mdns=yes
SSL wrapping is more difficult because it takes so many arguments, and we're not currently storing them but taking them from the config object directly.
So they would need to be copied as attributes in the server object so we can re-use them later.
comment:3 Changed 18 months ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 Changed 6 months ago by
As of r27656, the socket options can also be used to configure socket protocol upgrades:
xpra start --start=xterm --bind-tcp=0.0.0.0:10000,ssh=0,http=0,https=1,ssl=1,ssl-cert=./ssl-cert.pem
ie: this allows plain tcp and https / wss, bit not http or ssh upgrades.
comment:6 Changed 3 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2424
Note: See
TracTickets for help on using
tickets.
r23896 does this for
TCP_CORK
andTCP_NODELAY
, ie:Other things we can use this for: