> In a manner of speaking, yes. That is, Apache needs to have correctly
> configured VirtualHost directives to handle the requests from the
> outside world appropriately, and Zope needs to have the SiteAccess
> product installed with correctly configured SiteRoots and access rules.
> It takes a little bit of time to figure out, but it works like a charm
> and is really quite simple, once you wrap your head around it. There's
> a great HOW-TO on this at http://www.zope.org/Members/anser/apache_zserver.
I would also point you to
for more info on the apache side, particularly this bit:
The main disadvantage is that you cannot have a different log
file for each virtual host; however if you have very many virtual
hosts then doing this is dubious anyway because it eats file
descriptors. It is better to log to a pipe or a fifo and arrange
for the process at the other end to distribute the logs to the
customers (it can also accumulate statistics, etc.).
> Another benefit of this setup is that it can allow for both regular HTTP
> and SSL connections to all of your sites, so you can remotely access the
> manage screens without sending your passwords in the clear. A HOW-TO
> for this lives at http://www.zope.org/Members/unfo/apache_zserver_ssl.
> I still haven't figured out a clean way to make it impossible to access
> sensitive areas UNLESS you're using SSL, however. Anyone out there
> doing this?
mod_rewrite is your friend. You just make a Rule that redirects
anyone accessing your site on port 80 to port 443, something like
RewriteRule ^/(.*) https://www.foobar.com/
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -