Technically, no, you don't have a right to complain but you do have a very good point. I'd like to echo it and point out the problem is exacerbated by zope.org not having a strong way of marking docs and products as deprecated. I hate finding a cool product, downloading and installing, only to learn it fell out of fashion with 2.something. Ideally, such pages should be marked and linked to whatever is the latest greatest substitute or just marked as dead to Zopes 2.x+ I keep coming back to that scene in Apocalypse Now: "Who's in charge here, soldier?" "Ain't you?" http://www.rickmcginnis.com/movies/apocalypsenowredux.htm Granted, that's not a great metaphor for Zope but I do have that feeling with free software pretty often. FWIW, commercial development tools are often no better.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Jack Coates Sent: Monday, July 29, 2002 1:31 PM To: zope@zope.org 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/sit e_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/si te_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 )