On Sat, 11 Nov 2000, gene wrote: > This might be a little off-topic, but perhaps someone has > dealt with this here. I'm still trying to get the new > proxified apache mod_perl set up to work. > > First, since I have perl scripts in various places, I changed > this: > <IfDefine PERLPROXIED> > ProxyPass /perl/ http://127.0.0.1:8200/ > ProxyPassReverse /perl/ http://127.0.0.1:8200/ > </IfDefine> > > to this: > <IfDefine PERLPROXIED> > Rewrite on > RewriteRule ^(.*\.pl)$ http://127.0.0.1:8200/$1 [P] > ProxyPassReverse /perl/ http://127.0.0.1:8200/ > </IfDefine> The problem with that approach is that it forwards all perl scripts to mod_perl, which can be a bad thing, because most scripts are not designed for it. That's why the mod_perl people put the scripts in /perl, so only well behaved scripts get run with mod_perl. > I haven't tried that out, but I assume it would work fine for serving > a single domain, but I have several name-based virtual hosts. With the > configuration above, the proxy server wouldn't know which virtual host > was supposed to be responding. I started doing some more complicated > rewrite rules that would call the proxy server with the name of the > virtual server, but I wasn't sure if I was on the right track with > that. Maybe we could do: <IfDefine PERLPROXIED> ProxyPass /perl/ http://$1:8200/ ProxyPassReverse /perl/ http://$1:8200/ </IfDefine> And have both httpd.conf and httpd-perl.conf have the same "Include conf/vhosts/DynamicVhosts.conf" directive so you don't have to duplicate all your settings. It's just a suggestion, not tested. ------------------------------------------------------------ Jean-Michel Dault <[EMAIL PROTECTED]> MandrakeSoft inc, Montreal (Canada)
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
