VirtualHostMonster, PATH_INFO and absolute_url
Hi, I'm using VistualHostMonster in Zope 2.3b2 with this Apache virtual host: <VirtualHost 10.0.1.21:80> ProxyPass / http://10.0.1.20:8080/VirtualHostBase/http/10.0.1.21:80/MySite/VirtualHostRo... ProxyPassReverse / http://10.0.1.20:8080/VirtualHostBase/http/10.0.1.21:80/MySite/VirtualHostRo... ProxyPass /misc_ http://10.0.1.20:8080/misc_ ProxyPass /p_ http://10.0.1.20:8080/p_ </VirtualHost> I have a couple of problems with this setup: 1. When accessing http://10.0.1.21/spam PATH_INFO is /VirtualHostBase/http/10.0.1.21:80/MySite/VirtualHostRoot/spam, which breaks any method that uses PATH_INFO (For example, the login form of LoginManager). Can this be fixed somehow? 2. In this setup, if I got it right, absolute_url() for /MySite/spam should return http://10.0.1.21/spam. But it returns http://10.0.1.21/MySite/spam. Something's broken? -- Itai Tavor "Je sautille, donc je suis." C3Works itai@c3works.com - Kermit the Frog "If you haven't got your health, you haven't got anything"
2. In this setup, if I got it right, absolute_url() for /MySite/spam should return http://10.0.1.21/spam. But it returns http://10.0.1.21/MySite/spam. Something's broken?
I have this same problem. If the documentation in the VHM is correct, it's a bug. I found that adding a VHM to the /MySite folder (in addition to the root) "fixes" absolute_url(). I'm using FastCGI, but I imagine it'll work the same with ProxyPass. Perhaps I should take the time to report it in the Collector...unless you get to it first. _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
From: Itai Tavor <itai@optusnet.com.au>
1. When accessing http://10.0.1.21/spam PATH_INFO is /VirtualHostBase/http/10.0.1.21:80/MySite/VirtualHostRoot/spam, which breaks any method that uses PATH_INFO (For example, the login form of LoginManager). Can this be fixed somehow?
The Zope virtual hosting machinery doesn't adjust CGI variable. Applications should use URL0 or URLPATH0 instead of PATH_INFO.
2. In this setup, if I got it right, absolute_url() for /MySite/spam should return http://10.0.1.21/spam. But it returns http://10.0.1.21/MySite/spam. Something's broken?
Yep, VirtualHostMonster has a bug, now fixed in CVS. Thanks! Cheers, Evan @ digicool & 4-am
Evan Simpson wrote:
From: Itai Tavor <itai@optusnet.com.au>
1. When accessing http://10.0.1.21/spam PATH_INFO is /VirtualHostBase/http/10.0.1.21:80/MySite/VirtualHostRoot/spam, which breaks any method that uses PATH_INFO (For example, the login form of LoginManager). Can this be fixed somehow?
The Zope virtual hosting machinery doesn't adjust CGI variable. Applications should use URL0 or URLPATH0 instead of PATH_INFO.
I was thinking more along a fix at the Apache level... but it's not really very important, it was easy to hack PATH_INFO out of LoginManager and I've been planning to take it out of my own application anyway.
2. In this setup, if I got it right, absolute_url() for /MySite/spam should return http://10.0.1.21/spam. But it returns http://10.0.1.21/MySite/spam. Something's broken?
Yep, VirtualHostMonster has a bug, now fixed in CVS. Thanks!
Great, thanks for the fix. It's fine in Zope 2.3b3. -- -- Itai Tavor -- "Je sautille, donc je suis." -- itai@optusnet.com.au -- - Kermit the Frog -- -- 'Supposing a tree fell down, Pooh, when we were underneath it?' -- -- 'Supposing it didn't,' said Pooh after careful thought. --
From: "Itai Tavor" <itai@optusnet.com.au>
Great, thanks for the fix. It's fine in Zope 2.3b3.
I should probably write a Howto for VirtualHostMonster, and ask the folks who've written the various fine SiteAccess-related Howtos to incorporate it. It really is a lot easier and safer to use than SiteRoots 98% of the time. Cheers, Evan @ digicool & 4-am
I should probably write a Howto for VirtualHostMonster, and ask the folks who've written the various fine SiteAccess-related Howtos to incorporate it. It really is a lot easier and safer to use than SiteRoots 98% of the time.
I agree. It's very easy to use with Apache, and it doesn't mess up /manage access through the primary domain. Woohoo! _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
I should probably write a Howto for VirtualHostMonster, and ask the folks who've written the various fine SiteAccess-related Howtos to incorporate it. It really is a lot easier and safer to use than SiteRoots 98% of the time.
I would appreciate that HOWTO. :) I am going to need virtual hosting for a project I am undertaking and don't even know where to begin. Is VirtualHostMonster part of SiteAccess (which I have just discovered when I did a search on zope.org)? Do I need to use apache for it? Should I use apache rather than ZServer if I don't need any of apache's features? Thanks, Phil. -- Philip Aylesworth paylesworth@stclaircollege.ca
From: Philip Aylesworth <paylesworth@stclairc.on.ca>
I would appreciate that HOWTO. :) I am going to need virtual hosting for a project I am undertaking and don't even know where to begin. Is VirtualHostMonster part of SiteAccess (which I have just discovered when I did a search on zope.org)? Do I need to use apache for it? Should I use apache rather than ZServer if I don't need any of apache's features?
If you genuinely don't need Apache, ZServer is certainly good enough. Many people (such as myself) use Apache for a cheap management/performance win serving large utterly static content like images, for battle-tested SSL, and for the ability to run other back-end servers or CGI in parallel. VirtualHostMonster is a newish SiteAccess component that makes virtual hosting easy for the most common cases, where Apache or some other thin back-end is handling the incoming rewriting, and the rewriting consists of host/port renaming and path insertion (http://www.myhost.com/ => http://localhost:8080/myhost). In this case, all you need is one VirtualHostMonster and a slight, easy change to your rewrite/proxy directives. Cheers, Evan @ digicool & 4-am
participants (4)
-
Evan Simpson -
Itai Tavor -
Philip Aylesworth -
Ron Bickers