You need to take a sledge hammer to your config... get rid of almost
EVERYTHING. Here is a copy of mine..., oh, and you might want to look
back a few days, I posted a really good link about mod_proxy and
mod_rewrite. Or search apache's site for mod_proxy, or just proxy...
that's how I came up with that link. Anyhow... heres the config:
#
## apache-rproxy.conf -- Apache configuration for Reverse Proxy Usage
##
User nobody
Group nobody
# server type
ServerType standalone
Port 1080
MinSpareServers 2
StartServers 2
MaxSpareServers 2
MaxClients 16
MaxRequestsPerChild 100
# server operation parameters
KeepAlive on
MaxKeepAliveRequests 100
KeepAliveTimeout 15
Timeout 400
IdentityCheck off
HostnameLookups off
# paths to runtime files
PidFile /usr/local/apacheproxy/logs/apache-rproxy.pid
LockFile /usr/local/apacheproxy/logs/apache-rproxy.lock
ErrorLog /usr/local/apacheproxy/logs/elog
CustomLog /usr/local/apacheproxy/logs/dlog "%{%v/%T}t %h -> %{SERVER}e URL:
%U"
# unused paths
ServerRoot /usr/local/apacheproxy
DocumentRoot /tmp
CacheRoot /tmp
#RewriteLog /dev/null
TransferLog /dev/null
#TypesConfig /dev/null
AccessConfig /dev/null
ResourceConfig /dev/null
# speed up and secure processing
<Directory />
Options -FollowSymLinks -SymLinksIfOwnerMatch
# AllowOverwrite None
</Directory>
# the status page for monitoring the reverse proxy
#<Location /rproxy-status>
#SetHandler server-status
#</Location>
# enable the URL rewriting engine
#RewriteEngine on
#RewriteLogLevel 0
# define a rewriting map with value-lists where
# mod_rewrite randomly chooses a particular value
#RewriteMap server rnd:/path/to/apache-rproxy.conf-servers
# make sure the status page is handled locally
# and make sure no one uses our proxy except ourself
#RewriteRule ^/apache-rproxy-status.* - [L]
#RewriteRule ^(http|ftp)://.* - [F]
# now choose the possible servers for particular URL types
#RewriteRule ^/(.*\.(cgi|shtml))$ to://${server:dynamic}/$1 [S=1]
#RewriteRule ^/(.*)$to://${server:static}/$1
# and delegate the generated URL by passing it
# through the proxy module
#RewriteRule ^to://([^/]+)/(.*) http://$1/$2 [E=SERVER:$1,P,L]
# and make really sure all other stuff is forbidden
# when it should survive the above rules...
#RewriteRule .* - [F]
# enable the Proxy module without caching
ProxyRequests on
NoCache *
# setup URL reverse mapping for redirect reponses
ProxyPass / http://www.esdev.net/
ProxyPassReverse / http://www.esdev.net/
On Thu, Apr 27, 2000 at 05:41:36PM +0100, Matt Sergeant wrote:
> On Thu, 27 Apr 2000, Matt Sergeant wrote:
>
> > > 1 mod_perl process could handle all the load
> > > you could possibly generate, and just let the mod_proxies build up and
> > > you'll see a lot lower memory usage on your box... seriously, in low
> > > bandwidth situations if your using the box for more than hosting
> > > (which I'd be willing to put good money on you are) then mod_proxy
> > > stands to give you tremendous benefits in the amount of free resources
> > > for other programs.
> >
> > I'm going to try it. I'll let people know...
>
> OK, I can't figure this out.. help me out here. I want to deal with my
> virtual hosts on the heavyweight server. The frontend server should just
> be a simple thing that I never have to touch.
>
> But when I do:
>
> ProxyPass / http://127.0.0.1:8080/
> ProxyPassReverse / http://127.0.0.1:8080/
>
> I get all requests going to the default virtual host, not the virtual host
> I'm requesting...
>
> --
> <Matt/>
>
> Fastnet Software Ltd. High Performance Web Specialists
> Providing mod_perl, XML, Sybase and Oracle solutions
> Email for training and consultancy availability.
> http://sergeant.org http://xml.sergeant.org
>
