Just wondering if we could pass an already-opened-TCP-socket instance to
the browser.
Intention is just to prevent the socket-creation on the browser (instead
passing the already connected socket to the broswer), and let the browser
start over from there on.
Do I make sense?
On Fri, Mar 24, 2017
Hi All.
I could have the proxying to work perfectly, using the awesome step-by-step
link at
https://devops.profitbricks.com/tutorials/configure-apache-as-a-reverse-proxy-using-mod_proxy-on-ubuntu/.
Whenever I opened a URL of type http://Intermediatary/path/to/url in
*Server*'s browser, the content
Hi Rainer.
Thanks for the help.
I did some more googling, and (if I am not wrong), it seems
https://httpd.apache.org/docs/2.4/mod/mod_proxy_http.html almost fits in
our needs.
We run mod_proxy on the *Intermediatary*.
The end-user then opens a browser in *Server*, types in the hostname://path
of
> Now, we require something like opening an IFrame on the Server, and provide
> virtual access to the HTTP-Server (via Intermediatary), something like what
> Teamviewer does. We have the ability to modify to Server and Intermediatary,
> but not HTTP-Server in the general case.
>
> It would be great
Hi All.
We have the following architecture ::
Server <==> Intermediatary <==> HTTP-Server
*
Server and Intermediatary communicate over the internet as usual.
*
Intermediatary and HTTP-Server communicate over a local-interface.
HTTP-Server is reachable at the Intermediatary, but the HTTP-Serv
