Activate your mod_proxy module<br><br>I have the same problem some days ago with the same trackback and the activation of proxy module solves the problem<br><br><div><span class="gmail_quote">2007/3/23, Andreas Tille <<a href="mailto:tillea@rki.de">
tillea@rki.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I'm using an often recommended Apache-Zope rewrite setup to
<br>mask the internal folder structure in Zope. The cruxial line<br>in my apache (Debian Etch packaged version 2.2.3) is<br><br><br>RewriteRule ^(.*) <a href="http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/myfolder/VirtualHostRoot$1">
http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/myfolder/VirtualHostRoot$1</a> [P,L]<br><br><br>where a.b.c.d is the visible address of the machine from<br>outisde the firewall, myfolder the folder of my Zope<br>application I want to provide under
a.b.c.d:80<br>and as Debian users might are comfortable with 9673 the<br>Zope port (default for Debian).<br><br>This setup works fine for the old firewall which is not so<br>strict as the new one, that causes the trouble.
<br>The new one exclusively enables port 80 (no 22, 25 etc.).<br><br>If I try the rewrite rule above I get the following line in<br>error.log:<br><br>[<date>] [error] (110)Connection timed out: proxy: HTTP: attempt to connect to
a.b.c.d:9673 (*) failed<br><br>access.log says:<br><br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] "GET / HTTP/1.0" 503 405<br><br>For Debugging purpose I also write a debugging log:
<br><br> (the IP-Adress is replaced by a.b.c.d and the visible DNS name by <a href="http://visible.name">visible.name</a>)<br><br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] [<a href="http://visible.name/sid#81869c0][rid#81dc4c0/initial">
visible.name/sid#81869c0][rid#81dc4c0/initial</a>] (2) init rewrite engine with requested uri /<br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] [<a href="http://visible.name/sid#81869c0][rid#81dc4c0/initial">
visible.name/sid#81869c0][rid#81dc4c0/initial</a>] (3) applying pattern '^(.*)' to uri '/'<br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] [<a href="http://visible.name/sid#81869c0][rid#81dc4c0/initial">
visible.name/sid#81869c0][rid#81dc4c0/initial</a>] (2) rewrite '/' -> '<a href="http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/">http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/
</a>'<br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] [<a href="http://visible.name/sid#81869c0][rid#81dc4c0/initial">visible.name/sid#81869c0][rid#81dc4c0/initial</a>] (2) forcing proxy-throughput with
<a href="http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/">http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/</a><br><a href="http://194.95.177.123">194.95.177.123</a> - - [23/Mar/2007:13:46:58 +0100] [
<a href="http://visible.name/sid#81869c0][rid#81dc4c0/initial">visible.name/sid#81869c0][rid#81dc4c0/initial</a>] (1) go-ahead with proxy request proxy:<a href="http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/">
http://a.b.c.d:9673/VirtualHostBase/http/a.b.c.d:80/agi/VirtualHostRoot/</a> [OK]<br><br><br>This is exactly the rewrite log I get on the machine that works<br>perfectly behind the old firewall, but the niew one cases the
<br>strange error above.<br><br>When I searched the web with the string in my error.log I stumbled upon<br>the site<br><br> <a href="http://www.dharwadkar.com/weblog/apache_fc6_01">http://www.dharwadkar.com/weblog/apache_fc6_01
</a><br><br>which gives a slight hint, but there is no SELinux on my box at all but<br>there is a hint to the firewall that might cause the problem.<br><br>I have a vague suspection that this might be very slightly connected
<br>with the fact that when I formerly followed the recommendation of<br><br> <a href="http://plone.org/documentation/how-to/plone-with-apache-1.3">http://plone.org/documentation/how-to/plone-with-apache-1.3</a><br><br>
to use "localhost" instead of the IP Adress of the server (or the FQDN)<br>I blatantly failed because the localhost directive was interpreted by<br>my browser that tried to access a local server (that did not existed).
<br>So I learned by this that these Rewrite directives are not addressed<br>to the webserver to deliver a different page than requested but<br>to tell the browser to ask for a different page on the server. If<br>I think about this I wonder whether this is a reasonable strategy of
<br>redirection and because I do not regard this as reasonable I'm wondering<br>whether there is an option I could change this behaviour in a way that<br>the server directly answers with the result that can be obtained at
<br>the rewritten location - which would probably solve my problem.<br>If my suspection that the Browser is advised to obtain the<br> <a href="http://a.b.c.d:9673/.">http://a.b.c.d:9673/.</a>..<br>something address it is obviouse that this must fail because port
<br>9673 is blocked and there would never be a chance to get any page.<br><br>Kind regards<br><br> Andreas.<br><br>--<br><a href="http://fam-tille.de">http://fam-tille.de</a><br>_______________________________________________
<br>Zope maillist - <a href="mailto:Zope@zope.org">Zope@zope.org</a><br><a href="http://mail.zope.org/mailman/listinfo/zope">http://mail.zope.org/mailman/listinfo/zope</a><br>** No cross posts or HTML encoding! **<br>
(Related lists -<br> <a href="http://mail.zope.org/mailman/listinfo/zope-announce">http://mail.zope.org/mailman/listinfo/zope-announce</a><br> <a href="http://mail.zope.org/mailman/listinfo/zope-dev">http://mail.zope.org/mailman/listinfo/zope-dev
</a> )<br></blockquote></div><br><br clear="all"><br>-- <br>Mis Cosas<br><a href="http://blogs.sistes.net/Garito">http://blogs.sistes.net/Garito</a>