AW: [Zope] Caching prob with headers or reverse proxy?

[Germer, Carsten]

Sorry for the late answer.
Yes, that works :) but I would need to do a lot of work by hand.

I understand that "Accellerated HTTP Cache Manager" doesn't do the =
trick?
Why is it in the distribution then, anyway?

Is there a way to write a function that is called on delivery of =
_every_
object? I could write the cache headers in there and even set them =
different
based on Object type, Parameters, etc etc.
That would do the trick that AHCM should be doing and more.

/Gem

> -----Urspr=FCngliche Nachricht-----
> Von: Dylan Reinhardt [mailto:zope@dylanreinhardt.com]
> Gesendet: Donnerstag, 17. April 2003 16:57
> An: Germer, Carsten
> Cc: 'zope@zope.org'
> Betreff: Re: [Zope] Caching prob with headers or reverse proxy?
>=20
>=20
> On Thu, 2003-04-17 at 06:40, Germer, Carsten wrote:
> > Hi there,
> >=20
> > I have set up an Apache as reverse proxy and it works fine so far.
> > The actual problem is that I only get "image"s to cache, no =
pagelike
> > items...
>=20
> You'll need to add a couple headers to pages you want cached,
> instructing the cache as to how they should be handled.  I=20
> create a DTML
> method called cache_content that consists of:
>=20
> <dtml-call "RESPONSE.setHeader('Expires',
> _.DateTime(_.DateTime().timeTime() + 3600).toZone('GMT').rfc822())">
> <dtml-call "RESPONSE.setHeader('Last-Modified',
> bobobase_modification_time().toZone('GMT').rfc822())">
>=20
> And then can call that method from any page I want to be cached by
> Apache.
>=20
> HTH,
>=20
> Dylan
>=20
>=20