Re: [Zope] Basic problem with zope behind apache: no images, no frames, etc.
On Thu, 16 Dec 2004 10:27:30 -0500, Alan Snyder <alan8373@gmail.com> wrote:
Insert a SiteRoot object and enter the paramaters of the url, port and context of your apache virtual site or directory information. Zope embeds an html <base> tag in all its pages and will mess up users behind proxy servers without a correct siteroot in your project.
On Thu, 16 Dec 2004 16:04:48 +0100, Giuseppe Bonelli <giuseppe.bonelli@tiscalinet.it> wrote:
Are you using absolute urls in all your DTML/python scripts ...?
... and try this rewrite rule: ^/manage(*) .....
Hope this helps __peppo
-----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org]On Behalf Of roger baig vinas Sent: mercoledi 15 dicembre 2004 12.19 To: zope@zope.org Subject: [Zope] Basic problem with zope behind apache: no images, no frames,etc.
Hello,
I'm trying to set up a zope server behind an already existing and working fine apache on a debian/woody box with no X system installed. When I try say http://IPbox/manage I just get the skeleton of the page that it's suppossed to be forwarded and nothing else (no images, no contents, no etc.)
I tryed both ProxyPass and RewriteRule at http.d with the same results:
RewriteRule ^/(manage)\
http://localhost:9673/manage/VirtualHostBase/http/213.73.38.11 0:80/manage/VirtualHostRoot/$1\ [L,P]
ProxyPass /HelpSys http://localhost:9673/HelpSys ProxyPassReverse /HelpSys http://localhost:9673/HelpSys
You can see the results at http://213.73.38.110/HelpSys or at http://213.73.38.110/HelpSys with user:admin passwd:zope_admin
I've been readin a lot about VHM, and so forth, but now I don't know how to go on. Any help advice or suggestion will be apreciated.
Thank you in advance
||/ Name Version Description +++-=========================-=========================-=========== ii zope 2.5.1-1woody1 An Open Source Web Application Server ii apache 1.3.26-0woody6 Versatile, high-performance HTTP server
httpd.conf (section):
NameVirtualHost * <VirtualHost *> <IfModule mod_proxy.c> <IfModule mod_rewrite.c> RewriteEngine On RewriteLog "/var/log/apache/zope/rewrite.log" RewriteLogLevel 1
#http://zope.org/Members/regebro/Zope_and_Apache #http://www.zope.it/Members/mickymouse/zope_to_apache2/view?se archterm=Virtual%20Host%20Monster ##RewriteRule ^/(.*) http://localhost:8080/VirtualHostBase/http/www.virtualdomain.c om:80/www_virtualdomain_com/VirtualHostRoo RewriteRule ^/(manage)\
http://localhost:9673/manage/VirtualHostBase/http/213.73.38.110:80/manag e/VirtualHostRoot/$1\ [L,P]
#doesn't work: RewriteRule ^/(community) http://localhost:9673/VirtualHostBase/http/213.73.38.110:80/community/Vi rtualHostRoot/$1 [L,P] RewriteRule ^/(HelpSys) http://localhost:9673/HelpSys/VirtualHostBase/http/213.73.38.110:80/Help Sys/VirtualHostRoot/$1 [L,P]
</IfModule> </IfModule> </VirtualHost>
ProxyPass /HelpSys http://localhost:9673/HelpSys ProxyPassReverse /HelpSys http://localhost:9673/HelpSys
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Dec 16, 2004, at 16:27, Alan Snyder wrote:
On Thu, 16 Dec 2004 10:27:30 -0500, Alan Snyder <alan8373@gmail.com> wrote:
Insert a SiteRoot object and enter the paramaters of the url, port and context of your apache virtual site or directory information. Zope embeds an html <base> tag in all its pages and will mess up users behind proxy servers without a correct siteroot in your project.
SiteRoot objects are dangerous because they can lock you out of your Zope instance easily. They should *not* be used anymore. VirtualHostMonster is the way to go. It even has standalone virtual host mapping capabilities without using rewrite rules from proxies on its "Mappings" tab. jens --------------- Jens Vagelpohl jens@zetwork.com Software Engineer +49-(0)441-36 18 14 38 Zetwork GmbH http://www.zetwork.com/
Yeah - i know about that downside of siteroots. I'll have to learn VHM's next. On Thu, 16 Dec 2004 17:03:34 +0100, Jens Vagelpohl <jens@dataflake.org> wrote:
On Dec 16, 2004, at 16:27, Alan Snyder wrote:
On Thu, 16 Dec 2004 10:27:30 -0500, Alan Snyder <alan8373@gmail.com> wrote:
Insert a SiteRoot object and enter the paramaters of the url, port and context of your apache virtual site or directory information. Zope embeds an html <base> tag in all its pages and will mess up users behind proxy servers without a correct siteroot in your project.
SiteRoot objects are dangerous because they can lock you out of your Zope instance easily. They should *not* be used anymore. VirtualHostMonster is the way to go. It even has standalone virtual host mapping capabilities without using rewrite rules from proxies on its "Mappings" tab.
jens
---------------
Jens Vagelpohl jens@zetwork.com Software Engineer +49-(0)441-36 18 14 38 Zetwork GmbH http://www.zetwork.com/
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On 16.Dec 2004 - 17:03:34, Jens Vagelpohl wrote:
On Dec 16, 2004, at 16:27, Alan Snyder wrote: SiteRoot objects are dangerous because they can lock you out of your Zope instance easily. They should *not* be used anymore. VirtualHostMonster is the way to go. It even has standalone virtual host mapping capabilities without using rewrite rules from proxies on its "Mappings" tab.
Let me hook onto that: I have site that was created by be, but somebody else but it behind an apache and opened it to the web. I'd like to remove the SiteRoot, but this makes the port of zope visible to everybody :-( So the current config looks like this: The apache rewrites access to the servername to another hostname with the zope-Port like this: <VirtualHost server:80> ServerName fqdn_for_zope RewriteEngine On RewriteRule ^/(.*) http://fqdn_for_zope.de:8080/$1 [P] </VirtualHost> I have a VHM in zope to make ls-dbis the root for server: server/ls-dbis ls-dbis is the site and has a SiteRoot like this: Base: http://fqdn_for_zope.de Path: / As far as I understand it, this make the :8080 Port invisible when acessing the site. How can I do the same with apache-VirtualHost and VHM only? (Especially for the apache part I'm the wrong one) Andreas -- Beware of a tall black man with one blond shoe.
If you have a VHM, you don't need any SiteRoot anymore. there is a lot of documentation on how to use apache in front of zope... http://plone.org/documentation/howto/plone-with-apache-1.3 http://www.devshed.com/c/a/Zope/Using-Zope-With-Apache/ http://www.cheimes.de/opensource/docs/zope-apache2/ and another that helped me a lot for my first python/zope install from source: http://www.ctln.org/team/travis/careertech-webservers/config-and-install HTH Andreas Pakulat wrote:
On 16.Dec 2004 - 17:03:34, Jens Vagelpohl wrote:
On Dec 16, 2004, at 16:27, Alan Snyder wrote: SiteRoot objects are dangerous because they can lock you out of your Zope instance easily. They should *not* be used anymore. VirtualHostMonster is the way to go. It even has standalone virtual host mapping capabilities without using rewrite rules from proxies on its "Mappings" tab.
Let me hook onto that: I have site that was created by be, but somebody else but it behind an apache and opened it to the web. I'd like to remove the SiteRoot, but this makes the port of zope visible to everybody :-(
So the current config looks like this:
The apache rewrites access to the servername to another hostname with the zope-Port like this:
<VirtualHost server:80> ServerName fqdn_for_zope RewriteEngine On RewriteRule ^/(.*) http://fqdn_for_zope.de:8080/$1 [P] </VirtualHost>
I have a VHM in zope to make ls-dbis the root for server: server/ls-dbis
ls-dbis is the site and has a SiteRoot like this:
Base: http://fqdn_for_zope.de Path: /
As far as I understand it, this make the :8080 Port invisible when acessing the site. How can I do the same with apache-VirtualHost and VHM only? (Especially for the apache part I'm the wrong one)
Andreas
-- David Convent
On 17.Dec 2004 - 10:40:06, David Convent wrote:
If you have a VHM, you don't need any SiteRoot anymore.
there is a lot of documentation on how to use apache in front of zope... http://plone.org/documentation/howto/plone-with-apache-1.3 http://www.devshed.com/c/a/Zope/Using-Zope-With-Apache/ http://www.cheimes.de/opensource/docs/zope-apache2/
and another that helped me a lot for my first python/zope install from source: http://www.ctln.org/team/travis/careertech-webservers/config-and-install
HTH
No and Yes :-) The URL's didn't help me much, but I rediscovered the chapter in the zope-book about VHM :-) Last time I read it, I had no need to read carefully the part about VirtualHostRoot and VirtualHostBase. At that time I setup Zope only for development.. But with those 2 I can do all I need without SiteRoot :-) Thanks for giving a broad hint Andreas -- You will have good luck and overcome many hardships.
participants (4)
-
Alan Snyder -
Andreas Pakulat -
David Convent -
Jens Vagelpohl