----- "Howard" <[email protected]> wrote:
> Greg Donald wrote:
> > On Wed, Feb 10, 2010 at 3:26 PM, Howard <[email protected]> wrote:
> >> TNX for the response, Greg. That was the first configuration I
> put
> >> ProxyPass ad nausea in and no go. What is the function of
> >> sites-available/default versus sites-enabled/000-default (which is
> what I'm
> >> trying right now)?? Yet another Google search, sigh.
> >
> > 000-default is usually a symlink to default.
> >
> > You put vhost entry files in /etc/apache2/sites-available, then you
> > turn them on and off with symlinks to them in
> > /etc/apache2/sites-enabled.
> >
>
> Thank you. I shall move back in that direction.
>
> Which begs the next question. In the CentOS yada/yada/httpd.conf
> file,
> I did not have to build out the <Virtual Host> blah, blah, blah
> </Virtual Host> stuff. sites-available has the <Virtual Host>
> construction but I am getting confused about that functionality that
> is
> local to the host and that which is to be reverse proxied.
>
> Am I making this more complicated than needed. I sure ain't making it
> work!
Quick class on how debian/ubuntu are breaking down the apache configs
to try and make life nicer.
httpd.conf is the old way of doing everything here. So there should just
be an include to apache2.conf and the newer way of doing things.
apache2.conf should contain only the host generic configs, that that makes
apache stand up basically and get started.
mods-available/ contains the modules load and configs that are available for
your install. You can edit here, but it does not mean they are in use.
mods-enabled/ contains symlinks back to the mods-available/ and these are
in use. Remember that editing here edits in the mods-available/.
sites-available/ works like mods-available, create vhosts here to do any
site specific functionality.
sites-enabled/ symlinks back to sites-available. Sometimes you will prefix
the symlinks with numbers and such to ensure specific config read order.
Hopefully you have digested that.
Howard, for reverse proxy, I have dealt with that in the past by
building out virtual hosts. Set apache for namedvirtualhosts. Then build
a virtual host for each of the proxied machines and give it the information
needed for doing the reverse proxy such as where in the internal network
to proxy to.
Benefits are you configure only what you want to expose to the outside. You
can even put limitations easily enough on the proxy to limit access that
need to know external IPaddrs.
After looking at my install, make sure you linked to proxy_http.load,
proxy.load,
and proxy.conf in the mods-enabled.
And here is a virtual host setup I am using.
<VirtualHost _default_:80>
ServerName home.drunkenlogic.com
ServerAlias home.drunkenlogic.com *.home.drunkenlogic.com
#Redirect permanent / https://home.drunkenlogic.com/
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog /var/log/apache2/access.log combined
ErrorLog /var/log/apache2/error.log
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
ProxyRequests Off
ProxyVia On
ProxyPreserveHost On
ProxyPass / http://192.168.0.206/ retry=1
ProxyPassReverse / http://192.168.0.206/
<Proxy>
Order allow,deny
Allow from all
SetOutputFilter DEFLATE
</Proxy>
</VirtualHost>
--
Steven Critchfield [email protected]
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
