You can have one HTTPS/SSL per IP per port.

I use Pound instead of Apache, and can run an instance for each port.

I use HTTPS on port 444, and 445 for testing/staging arrangements that match the production HTTPS on 443. I can set up a self-signed or 3rd party certificate for each port, and the domain is set in each new certificate. And simply use a standard web page to redirect to the new HTTPS port. (

Also, you can use Pound to virtual host SSL sites, but the certificate will not match, and a warning to the user. If you accept the warning, you are secure, but not very friendly.

Pound can be found at  and is very Zope friendly.

This is not a user-friendly solution for production-level sites, but great for staging/testing/experimental/admin needs.
Not sure, if this helps,


michael nt milne wrote:

I've got a few Plone sites set-up using Apache through Zope. The question is, I'd like to implement SSL on the site login etc, as it's not secure without this. There's also one site I'd like to serve completely over https. However. I'm told that you can't run SSL on virtual hosts and can only have once SSL site per IP address.

What would be the way round this? I know I could set-up SSL on Zope only using the following documentation:

but if I can't carry this through to Apache then I'd have to run Zope as the web server as well as the application server.



Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Jonathan Cyr

Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to