Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiplexing a web server through the same port as the xpra server #474

Closed
totaam opened this issue Dec 14, 2013 · 6 comments
Closed

multiplexing a web server through the same port as the xpra server #474

totaam opened this issue Dec 14, 2013 · 6 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Dec 14, 2013

Issue migrated from trac ticket # 474

component: server | priority: minor | resolution: fixed

2013-12-14 11:27:40: totaam created the issue


Similar to #426, but this will allow us to only intercept xpra packets, regular packets can be forwarded to a web server which can respond to regular HTTP packets.

[[BR]]

immediate benefits:

  • a scan will show the port as belonging to the web server and xpra remains hidden
  • we can server an html5 client page (html5 client #473) through the same server port
@totaam
Copy link
Collaborator Author

totaam commented Dec 14, 2013

2013-12-14 11:28:54: totaam uploaded file multiplex-web.patch (10.0 KiB)

PoC patch which does the multiplexing for http get requests only in "ServerBase"

@totaam
Copy link
Collaborator Author

totaam commented Dec 14, 2013

2013-12-14 14:29:56: totaam changed owner from antoine to smo

@totaam
Copy link
Collaborator Author

totaam commented Dec 14, 2013

2013-12-14 14:29:56: totaam commented


r4948 implements this and will allow us to do #473 much more easily.

Here's how to test:

  • start a web server on port 8000:
thttpd -p 8000
  • verify you can browse to it:
xdg-open http://SERVERIP:8000/
  • start an xpra server with the tcp proxy option pointing to this web server we have just started:
xpra start :10 --bind-tcp=10000 --start-child=xterm --tcp-proxy=127.0.0.1:8000
  • verify you can attach to this server:
xpra attach tcp:SERVERIP:10000
  • verify you can hit the web server on this same port, ie: open your browser at:
http://SERVERIP:10000/

@totaam
Copy link
Collaborator Author

totaam commented Dec 18, 2013

2013-12-18 02:46:52: smo changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Dec 18, 2013

2013-12-18 02:46:52: smo changed resolution from ** to fixed

@totaam
Copy link
Collaborator Author

totaam commented Dec 18, 2013

2013-12-18 02:46:52: smo commented


Tested on Fedora 19 and Fedora 20 x86_64 with no issues.

@totaam totaam closed this as completed Dec 18, 2013
@totaam totaam mentioned this issue May 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant