Zope + Apache + mod_proxy + SiteRoot = some links not proxied?
Hello readers, I've spent quite some time looking around for the "right" procedure to integrate Zope and Apache. I use mod_proxy as described in a number of places, especially: http://www.zope.org/Members/anser/apache_zserver I've followed the instructions step by step and it "mostly" works, meaning that *some* links do not work: - the "... folder at /..." link at the top of the main frame in ZMI - the top-right menu (quick start, prefs, logout) in ZMI - the ZMI link in the home (quick start) page - ... These links do not get rewritten to get "/zope" prepended to the local path part, so they give an error 404. All other links work, though, so I think that my setup is "almost" right. Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct? Base is "http://my-server.my-domain.com/zope" Path is "/" To somewhat work around this problem, I have had to add a bunch of extra ProxyPass statements in Apache's configuration, like: ProxyPass /manage_page_style.css http://my-server.my-domain.com:8080/manage_page_style.css ProxyPass /manage_workspace http://my-server.my-domain.com:8080/manage_workspace ProxyPass /manage_zmi_logout http://my-server.my-domain.com:8080/manage_zmi_logout ProxyPass /manage_zmi_prefs http://my-server.my-domain.com:8080/manage_zmi_prefs ProxyPass /zope_quick_start http://my-server.my-domain.com:8080/zope_quick_start ProxyPass /manage http://my-server.my-domain.com:8080/manage ProxyPass /HelpSys http://my-server.my-domain.com:8080/HelpSys ProxyPass /Examples http://my-server.my-domain.com:8080/Examples ProxyPass /manage_importObject http://my-server.my-domain.com:8080/manage_importObject This is probably not the right approach, but I can't find what is wrong in my setup. Thanks in advance for any help, Greets, _Alain_ -- Alain Fauconnet IT Technical Manager Asian Institute of Technology
En/na Alain Fauconnet ha escrit:
Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct?
Look here: http://plone.org/documentation/how-to/plone-with-apache-1.3 It's not plone specific and the links at the top are useful for other situations. E.g., if you follow http://zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.stx you'll read: "SiteRoots are an artifact of an older generation of Zope virtual hosting services that are only retained in current Zope versions for backwards-compatibility purposes. They are not documented in this book because they are somewhat "dangerous" for new users, as they have the capability of temporarily "locking you out" of your Zope instance if you configure them improperly. Luckily, we have Virtual Host Monsters, which do everything that SiteRoots do and more without any of the dangerous side effects of SiteRoots. If you want to do virtual hosting in Zope, you should almost certainly be using a Virtual Host Monster." Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
Luca, On Mon, Apr 10, 2006 at 12:13:58PM +0200, Luca Olivetti wrote:
En/na Alain Fauconnet ha escrit:
Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct?
Look here: http://plone.org/documentation/how-to/plone-with-apache-1.3
It's not plone specific and the links at the top are useful for other situations.
Thanks for your informative reply. I'm reading this page right now and I just have a question: I don't do virtual hosting at all. This box hosts a single web server. Does that still apply to me?
E.g., if you follow http://zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.stx you'll read:
"SiteRoots are an artifact of an older generation of Zope virtual hosting services that are only retained in current Zope versions for backwards-compatibility purposes. They are not documented in this book because they are somewhat "dangerous" for new users, as they have the capability of temporarily "locking you out" of your Zope instance if you configure them improperly. Luckily, we have Virtual Host Monsters, which do everything that SiteRoots do and more without any of the dangerous side effects of SiteRoots. If you want to do virtual hosting in Zope, you should almost certainly be using a Virtual Host Monster."
Hrmm. so basically this SiteRoot method is obsolete, right? Too bad all the stuff I could find by doing Google searches and from the Plone Live book still point at this method... Greets, _Alain_
En/na Alain Fauconnet ha escrit:
Thanks for your informative reply. I'm reading this page right now and I just have a question: I don't do virtual hosting at all. This box hosts a single web server. Does that still apply to me?
Yes, you can either make zope the root of your only server or map it to a subdirectory. VirtualHostMonster and a couple of rewrite rules can do both. I think that those links explain all the possibilities. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007
Alain Fauconnet wrote:
Luca,
On Mon, Apr 10, 2006 at 12:13:58PM +0200, Luca Olivetti wrote:
En/na Alain Fauconnet ha escrit:
Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct? Look here: http://plone.org/documentation/how-to/plone-with-apache-1.3
It's not plone specific and the links at the top are useful for other situations.
Thanks for your informative reply. I'm reading this page right now and I just have a question: I don't do virtual hosting at all. This box hosts a single web server. Does that still apply to me?
If you are only running a single site, have you considered using the Zope server exclusively? Unless there are sections of your site that you do not want Zope to handle, you wouldn't need Apache. -- Good day, eh. Chris
Alain Fauconnet schrieb:
Hello readers,
I've spent quite some time looking around for the "right" procedure to integrate Zope and Apache. I use mod_proxy as described in a number of places, especially: http://www.zope.org/Members/anser/apache_zserver I've followed the instructions step by step and it "mostly" works, meaning that *some* links do not work: - the "... folder at /..." link at the top of the main frame in ZMI - the top-right menu (quick start, prefs, logout) in ZMI - the ZMI link in the home (quick start) page - ... These links do not get rewritten to get "/zope" prepended to the local path part, so they give an error 404.
All other links work, though, so I think that my setup is "almost" right.
Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct? Base is "http://my-server.my-domain.com/zope" Path is "/"
To somewhat work around this problem, I have had to add a bunch of extra ProxyPass statements in Apache's configuration, like:
ProxyPass /manage_page_style.css http://my-server.my-domain.com:8080/manage_page_style.css ProxyPass /manage_workspace http://my-server.my-domain.com:8080/manage_workspace ProxyPass /manage_zmi_logout http://my-server.my-domain.com:8080/manage_zmi_logout ProxyPass /manage_zmi_prefs http://my-server.my-domain.com:8080/manage_zmi_prefs ProxyPass /zope_quick_start http://my-server.my-domain.com:8080/zope_quick_start ProxyPass /manage http://my-server.my-domain.com:8080/manage ProxyPass /HelpSys http://my-server.my-domain.com:8080/HelpSys ProxyPass /Examples http://my-server.my-domain.com:8080/Examples ProxyPass /manage_importObject http://my-server.my-domain.com:8080/manage_importObject
This is probably not the right approach, but I can't find what is wrong in my setup.
I fear the resource you discovered is wrong and old. Today, you have VirtualHostmonster (the "virtual_hosting" - object you have in your Zope-Root per default) to take care of rewriting the addresses. You only change the Rewrites to signal the hostname you want to zope. (Virtual-Host-Monster has hints for the format in its management interface - you dont need to configure anything there, just read the example) I usually dont use ProxyPass but mod_rewrite directly: RewriteEngine On RewriteRule ^/(.*) http://10.100.100.1:3128/VirtualHostBase/http/%{HTTP_HOST}:80/VirtualHostRoot/$1 [P,L] 10.100.100.1:3128 is the host:port zope listens. HTH Tino Wildenhain
Tino, On Mon, Apr 10, 2006 at 12:58:10PM +0200, Tino Wildenhain wrote:
Alain Fauconnet schrieb:
Hello readers,
I've spent quite some time looking around for the "right" procedure to integrate Zope and Apache. I use mod_proxy as described in a number of places, especially: http://www.zope.org/Members/anser/apache_zserver I've followed the instructions step by step and it "mostly" works, meaning that *some* links do not work: - the "... folder at /..." link at the top of the main frame in ZMI - the top-right menu (quick start, prefs, logout) in ZMI - the ZMI link in the home (quick start) page - ... These links do not get rewritten to get "/zope" prepended to the local path part, so they give an error 404.
All other links work, though, so I think that my setup is "almost" right.
Am I missing something? I have created the SiteRoot object in the root (/) folder. Is this correct? Base is "http://my-server.my-domain.com/zope" Path is "/"
(...)
I fear the resource you discovered is wrong and old. Today, you have VirtualHostmonster (the "virtual_hosting" - object you have in your Zope-Root per default) to take care of rewriting the addresses. You only change the Rewrites to signal the hostname you want to zope. (Virtual-Host-Monster has hints for the format in its management interface - you dont need to configure anything there, just read the example)
I usually dont use ProxyPass but mod_rewrite directly:
RewriteEngine On RewriteRule ^/(.*) http://10.100.100.1:3128/VirtualHostBase/http/%{HTTP_HOST}:80/VirtualHostRoot/$1 [P,L]
10.100.100.1:3128 is the host:port zope listens.
Thanks for the detailed reply. I'm looking into this now. I'm still confused by mod_rewrite vs. mod_proxy though. My Zope/Plone site is supposed to eventually get a lot of hits. Although it's hosted on a kind of high-end box, I have real concerns about the level of performance that will be obtained. Hence mod_proxy looked appealing because it's supposed to deliver higher performance than Zope's own HTTP server, right? It seems that more and more people use mod_rewrite instead. Isn't this a much more pass-through approach than mod_proxy? (especially if I turn some caching on - not something I've seen covered anywhere). By "more pass-through" I mean that clients end up taking to Zope's own HTTP server directly, with all the performance problems mentioned here and there. Would you please hint me on the rationale behind choosing between mod_proxy and mod_rewrite? I'm quite fuzzy on this now. Greets, _Alain_
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11 Apr 2006, at 01:19, Alain Fauconnet wrote:
It seems that more and more people use mod_rewrite instead. Isn't this a much more pass-through approach than mod_proxy? (especially if I turn some caching on - not something I've seen covered anywhere). By "more pass-through" I mean that clients end up taking to Zope's own HTTP server directly, with all the performance problems mentioned here and there. Would you please hint me on the rationale behind choosing between mod_proxy and mod_rewrite? I'm quite fuzzy on this now.
mod_rewrite *uses* mod_proxy if you create rules that include the "P" flag in the flags that are at the end of the rule. "P" stands for Proxy. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEO2i5RAx5nvEhZLIRApOyAKCGRRqHLIPLXAOnmeKvlqhlB7AQKwCdHsH3 Nesm32pEzpOIjsvdhIWHw7U= =nzuN -----END PGP SIGNATURE-----
Alain Fauconnet wrote: reply.
I'm looking into this now. I'm still confused by mod_rewrite vs. mod_proxy though. My Zope/Plone site is supposed to eventually get a lot of hits. Although it's hosted on a kind of high-end box, I have real concerns about the level of performance that will be obtained. Hence mod_proxy looked appealing because it's supposed to deliver higher performance than Zope's own HTTP server, right?
From what I have read, the Zope server is the most efficient way to serve pages from your Zope database. That's what it was designed to do. -- Good day, eh. Chris
participants (5)
-
Alain Fauconnet -
Chris Purves -
Jens Vagelpohl -
Luca Olivetti -
Tino Wildenhain