I sympathize with this, it's a real job keeping up with Zope developments. But one person every couple of days locks themselves out of their site using a SiteRoot, and runs screaming to this list. ;-) Evan or someone else usually talks them down from the tower in gentle tones, but it's still... well, it's annoying. This is why VirtualHostMonsters are better.. they're inert unless you actually use them. And they do everything that SiteRoots do. Personally, I want to nuke SiteRoots out of Zope but I don't think it's going to happen (because lots of folks use and like them), so no worries in any case. They're going to stay around, probably until the bits fall out of them. We'll just need to prop Evan and a couple of other folks up in front of their PCs 24x7 to deal with the poor souls who innocently fill out a form and then find they can no longer access any of their data. ;-) - C ----- Original Message ----- From: "Jack Coates" <jack@monkeynoodle.org> To: <zope@zope.org> Sent: Monday, July 29, 2002 4:31 PM Subject: Re: [Zope] future direction (was "problems with SiteRoot in Zope2.5.1")
So, speaking as a perennial Zope newbie, I have to say that I'm getting nervous about seeing all the things that I use fall one-by-one into the "that's depreciated, use this other cool product instead." I don't think I have a right to complain, but I'm complaining any way :-)
Jack
On Mon, 2002-07-29 at 10:04, Evan Simpson wrote:
Chris Withers wrote:
Yes, SiteRoots are no longer in favour with the powers that be. I still think they have their uses ;-)
Citizen Withers, your statement violates the Happy Voluntary Product Guidelines. Please report to the nearest PTB Help Station for assistance. ;-)
Does anybody know whether it is possible to have a configuration with both http and https directing to the same pages like the example in the above mentioned document (apache_zserver_ssl)?
Ria, we'll need more info on the problem you're having in order to help. If you do decide to try VHM, you should be able to get what you want with the following steps:
1. Create a VHM in your Zope root. Call it whatever you like, as long as the name doesn't clash with other objects ids, perhaps "vhm".
2. In the Apache VirtualHost section for port 80, replace the ProxyPass and ProxyPassReverse lines with the single line:
ProxyPass /
http://zope_server:8080/VirtualHostBase/http/www.domain.com:80/site_ path/VirtualHostRoot/
3. In the Apache VirtualHost section for port 443 (https),
replace the
ProxyPass and ProxyPassReverse lines with the single line:
ProxyPass /
http://zope_server:8080/VirtualHostBase/https/www.domain.com:80/site _path/VirtualHostRoot/
In the examples above, "zope_server:8080" is the host/port on
which your
Zope is listening, "www.domain.com" is your site's domain name, and "site_path" is the path from the root of your Zope to the Folder which contains this site (leave it out if your site lives in the Zope root).
You can determine whether a particular request uses SSL by checking "REQUEST['URL'].startswith('https')".
Cheers,
Evan @ 4-am
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Jack Coates Monkeynoodle: A Scientific Venture...
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )