httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajay Garg <ajaygargn...@gmail.com>
Subject Re: [users@httpd] Some basic (idiotic) queries regarding tunnelling-proxy
Date Fri, 24 Mar 2017 07:42:42 GMT
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 at 10:14 AM, Ajay Garg <ajaygargnsit@gmail.com> wrote:

> 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
> contents of page http://HTTP-Server/path/to/url opened up.
>
> Still, this requires the *Intermediatary* to have a public static
> IP-Address.
> Can this be done away with?
>
> Will be grateful for any replies.
>
>
> Thanks and Regards,
> Ajay
>
>
> On Wed, Mar 22, 2017 at 11:22 PM, Ajay Garg <ajaygargnsit@gmail.com>
> wrote:
>
>> 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 the *Intermediatary*, and the mod_proxy then proxies the
>> HTTP-stuff bi-directionally between the *HTTP-Server* and *Server*.
>>
>> My only concern, is that this solution needs the *Intermediatary* to have
>> a public static IP.
>> Is there a way objective can be achieved without needing to provide a
>> public static IP to *Intermediatary*?
>>
>>
>>
>>
>> On Wed, Mar 22, 2017 at 8:26 PM, Rainer Canavan <
>> rainer.canavan@sevenval.com> wrote:
>>
>>> > 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 to have a Teamviewer-like experience, providing
>>> access of
>>> > the HTTP-Server on the Server (via Intermediatary as the
>>> tunnelling-proxy).
>>> > We are running Linux-flavours on Server and Intermediatary.
>>>
>>> I don't understand what half of your statements may exactly mean, but
>>> this doesn't appear to be an apache httpd related request. I think
>>> the dynamic proxy option of most ssh clients (-D for openssh), used
>>> as a SOCKS proxy in your browser may solve your problem. If that
>>> doesn't help, some sort of VPN tunnel may be an alternative.
>>>
>>> rainer
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>> For additional commands, e-mail: users-help@httpd.apache.org
>>>
>>>
>>
>>
>> --
>> Regards,
>> Ajay
>>
>
>
>
> --
> Regards,
> Ajay
>



-- 
Regards,
Ajay

Mime
View raw message