Re> another newbie rewrite problem
I got it working! Thanks for the prompt replies. I have to say that while the documentation for Zope can be -er - challenging, the quick response from the community is great to see. The problem was not having the proxy modules loaded. It would appear that Apache 2 has a more elaborate scheme for proxy modules, and the tutorial at www.zope.org/Members/ike/Apache2_freeBSD also helped, by alerting me to the proxy module loading order. This is what I added to the bottom of the LoadModule sequence: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so Eventually, my virtual host set up looked like this: NameVirtualHost 10.1.3.225 <VirtualHost 10.1.3.225> ServerName www.dantest.com ServerAlias dantest.com DocumentRoot /var/www/html RewriteEngine On RewriteLog /dan/rwLog2.txt #RewriteLogLevel 9 #RewriteCond %{HTTP:Authorization} ^/(.*) RewriteRule /Zope/(.*) http://10.1.3.225:8080/VirtualHostBase/http/%{HTTP_HOST}:80/dantest/$1 [L,P] </VirtualHost> The road ahead is clear.... Pedal to the metal. dan DAN DONALDSON Webmaster UNICEF Canada ddonaldson@unicef.ca www.unicef.ca Tel.: 416 482-4444 ext. 890 Fax: 416 482-8035
Dan Donaldson wrote:
I got it working! Thanks for the prompt replies. I have to say that while the documentation for Zope can be -er - challenging, the quick response from the community is great to see.
The problem was not having the proxy modules loaded. It would appear that Apache 2 has a more elaborate scheme for proxy modules, and the tutorial at
Dan, one word of caution about apache2. I don't know about redhat, but Suse (8.1) comes with apache 2.0.40 (IIRC). This version is not production quality, as far as some feature are concerned that are quite typical to be used with zope. (Disk based) caching and mod_proxy in virtual hosts didn't work for me, and I can confirm this is indeed a bug (known to the apache developers). The problem was that this wasn't documentend prominently, and the bug just caused apache to never deliver pages from the cache, while it still created files in the cache dir. I found this out only because I was doing some benchmarks. So, if you don't need apache2 features, I'd consider using apache 1. cheers, oliver
participants (2)
-
Dan Donaldson -
Oliver Bleutgen