Itamar Shtull-Trauring wrote:
> Problem 1: HTTP and HTTPS (more of a proxypass issue)
> I want to be able to serve both http and https versions of a site from
> Apache. Problem is, because of the way proxying works, there is no way for
> Zope to know if it is origially being accessed via http or https.
There is a patch for apache which removes this problem, IIRC,
[EMAIL PROTECTED] may be able to help more with that...
> solution? Add a folder in top level of Zope called "ssl". If we see our
> path as proxied by Apache is /ssl/websites/example, we know we are being
> accessed via SSL. Because of the magic of acquisition, this works, but it's
> still an ugly hack,
Why is it an ugly hack? Seems like quite a graceful solution to me...
> and slows things down.
By how much? And why is this? I didn't the acquisiton caused a loss in
> Here's the SiteAccess rule I
> if REQUEST['PATH_INFO'][:5] == '/ssl/':
What difference does it make if you do REQUEST.setVirtualRoot('/',1)?
> REQUEST.setServerURL(protocol='https', hostname='www.example.com',
Not sure about that port... IIUC, setServerURL should mean that all the
links on your site contain:
...is that what you want?
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -