[Zope] Caching How-To (was Cache concerns (was zope/proxy_pass configuration problem) configuration problem)

[Ragnar Beer]

During the last couple of days I could finally figure out how to set 
up caching with mod_proxy. This morning I put together a caching 
howto and submitted it for review.

If it's accepted it will be available under 
http://www.zope.org/Members/rbeer/caching

I'm going on holiday now (Crete: wonderful greek island) and I'm 
going without my laptop so I won't answer any emails for the next two 
weeks ;)

Ragnar

>Ragnar,
>
>Caching is a subject I'm not all that familiar with but one I need to learn
>really fast.  My site is about to go live, and I have a monster of a query
>that will bring my system to its knees if 100 students run it at a time.  So
>I'm sending this off to the Zope mailing list wondering if anyone can give
>us some caching/performance tips.
>
>- T.J.
>
>-----Original Message-----
>From: Ragnar Beer [mailto:rbeer@uni-goettingen.de]
>Sent: Wednesday, August 02, 2000 12:48 PM
>To: T.J. Mannos
>Subject: RE: [Zope] zope/proxy_pass configuration problem
>
>
>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
>http://www.dummy.com/index_html shows 100 queries in Z2.log where
>there should be only one.
>What could I be doing wrong?
>
>Ragnar
>
>>Ragnar,
>>
>>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,
>>T.J.
>>
>>-----Original Message-----
>>From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of
>>Ragnar Beer
>>Sent: Wednesday, August 02, 2000 1:30 AM
>>To: zope@zope.org
>>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?
>  >
>  >Ragnar
>  >
>  >_______________________________________________
>  >Zope maillist  -  Zope@zope.org
>  >http://lists.zope.org/mailman/listinfo/zope
>  >**   No cross posts or HTML encoding!  **
>>(Related lists -
>>   http://lists.zope.org/mailman/listinfo/zope-announce
>>   http://lists.zope.org/mailman/listinfo/zope-dev )
>
>
>_______________________________________________
>Zope maillist  -  Zope@zope.org
>http://lists.zope.org/mailman/listinfo/zope
>**   No cross posts or HTML encoding!  **
>(Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )