search

FreeRDP / FreeRDP-WebConnect

A gateway for seamless access to your RDP-Sessions in any HTML5-compliant browser
519 stars 1.62k forks source link

Ever consider separating the web server from webConnect? #111

Open ghost opened 9 years ago

ghost commented 9 years ago

First is there a better place I should be asking question like this?

So rather than have:

browser --> webConnect

have:

browser --> webServer <-- webConnect

Web Connect would just need to use Web sockets to connect to the web server and wait. The browser would use web sockets to connect to the webServer and then use the existing web socket to communicate with webConnect.

This way webConnect would tunnel out using port 80 or port 443 thus bypassing most firewalls.

c64cosmin commented 9 years ago

@tmakaro Separating the webServer from webConnect is in our TODO list. It's not top priority right now. If you want to change the listening ports, for now you could just simply change them in wsgate.ini and configure your certificate. Refer to this sample: https://github.com/FreeRDP/FreeRDP-WebConnect/blob/master/wsgate/wsgate.ini.sample.in