here's an edited repost from an answer I got from this mailing list.
it has helped me with zope+apache (+ ssl) and is a good start for the
documentation upgrade, (although I personally use the apache proxypass directives)

-- original help from Leonardo Rochael Almeida <[EMAIL PROTECTED]> --

Here is how you'd do it with VirtualHostMonster and apache:

1. add a single one virtual host monster to your Zope root. Give it any
id you want. You can be creative, 'cause it won't matter :-)

2. In apache, change your configuration to read like below. To
understand why the ProxyPass urls read like that, look at the
VirtualHostMonster object or consult the SiteAccess2 documentation here:

### Apache ###

# better to use the IP address instead of the name here,
# to avoid dns lookups on apache initialization

# better to use the IP address here too, for the same reason
# here you put the server name instead of the address.
# it won't result in a dns lookup.
# secure /private
RedirectMatch permanent ^/private$1
# the :80 below is NECESSARY. Don't ommit it
ProxyPass /


# note the protocol specification after VirtualHostBase. As above,
# the port specification is not optional
ProxyPass /
SSLEngine on
SSLCertificateFile /etc/httpd/ssl.crt/server.crt
SSLCertificateKeyFile /etc/httpd/ssl.key/server.key


I haven't tested the configuration above. I'd use RewriteRules instead
of RedirectMatch and ProxyPass, but just because that's what I'm used to

Notice that ProxyPassReverse directives aren't needed, because the
VirtualHostMonster, when presented with the above URLs, effectively
convinces Zope that it's running in the above mentioned ports and

No SiteRoot objects are needed.
----------------------- end of original help ---------------

have fun,


"Science can amuse and fascinate us all,
but it is engineering that changes the world."
Isaac Asimov

Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - )

Reply via email to