Very good idea! I tried it and it works like a charm :) Thanks a lot!

One problem is left over: apache doesn't cache the documents although I have

<dtml-call "RESPONSE.setHeader('Expires', 
_.DateTime(_.DateTime().timeTime() + 3600).toZone('GMT').rfc822())">

in my standard_html_header. ab -n 100 -c 1 shows 100 queries in Z2.log where 
there should be only one.
What could I be doing wrong?


>If you're referring to my ZServer+Apache+SSL HOWTO, this would be a problem.
>Going in through https will only give you access to the 'ssl' directory.
>The quick & dirty solution (while retaining the ability to distinguish
>between http and https) is to reverse the setup, i.e. place the https
>SiteRoot in the main folder and create a separate folder called, say,
>'http', which holds the http SiteRoot.  This solution will kill two birds
>with one stone: it will grant access to the entire site via https while
>restricting http users to an empty subdirectory.
>Hope this helps,
>-----Original Message-----
>Ragnar Beer
>Sent: Wednesday, August 02, 2000 1:30 AM
>Subject: [Zope] zope/proxy_pass configuration problem
>Hi Zope-Configuristas!
>I would finally like to say goodbye to pcgi but one thing keeps me
>hooked. I tried and tried but the solution just won't appear. Here is
>the problem:
>I have a site that is supposed to be reachable via http as well as
>via https. That's not a problem per se. Configuration of zope with
>proxy_pass is easy as can be. The problem is that management shall be
>possible via https _only_ (for obvious reasons). But as soon as I use
>site access to define the http-branch this branch is not
>managable/accessable via https any more. Is there a solution?
>Zope maillist  -  [EMAIL PROTECTED]
>**   No cross posts or HTML encoding!  **
>(Related lists -
> )

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

Reply via email to