[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] OT: Reverse proxy for internal websites



The apache module mod_proxy is the stuff.  You can set up a proxy
defined in your virtual hosts section of httpd.conf.  Something like:

<VirtualHost 10.1.1.2:80>
#    ServerAdmin webmaster dummy-host example com
    ServerName your.hostname.com
ProxyRequests Off
ProxyPreserveHost On

<Proxy *>

Order deny,allow
Allow from all
</Proxy>

ProxyPass / http://10.1.1.3/
ProxyPassReverse / http://10.1.1.3/
</VirtualHost>


HTH,
Peter

On Jan 7, 2008 9:56 AM, David Hopkins <dahopkins429 gmail com> wrote:
> This query is rather off-topic, but perhaps someone on the list has
> implemented it.
>
> I want to be able to serve several different internal websites via
> http and https but only have one redirect at the router for ports 80
> and 443 to an internal system.  I can run squid or apache2 or both on
> that internal system.  What I had in mind was setting up this internal
> system to redirect the external requests to the appropriate internal
> servers based on the hostnames. The internal network uses a 10.
> address space if that makes a difference.  Both squid and apache2 can
> be set up for reverse proxying.  Has anyone on the list implemented
> this and is there a preference for which one to use?
>
> Sincerely,
> Dave Hopkins
> Newark Charter School
> Newark Delaware
>
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]