-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Oliver Bleutgen Sent: Tuesday, April 22, 2003 5:22 PM To: zope@zope.org Subject: Re: [Zope] Re: Accelerating images without proxy
Charlie Reiman wrote:
I checked the logs and then some HTML. We did tell the web designers (customer's choice of design agency) to reference all images with absolute url (well, always start with the slash, e.g "/images/navigation/home.gif", but they didn't (so they are: "images/navigation/home.gif"). And there are hardly any 304 codes in the log.
Would in this case an Accelerated HTTP Cache Manager help?
Yes, it will.
Not to nitpick, just to clarify for Marc, but no headers (that I know of) will help any proxy/browser cache to find out that /images/navigation/home.gif is the same image as /spam/images/navigation/home.gif Taken to the extreme, there could be an enourmous amount of strings instead of "spam" -> uncacheable. So, how would an AHCM help?
cheers, oliver
I guess I misread the posting. Generally in zope you don't use direct URL at all to refer to an image. You should instead get the object and ask it what it's URL is. If they must place image URLs in raw text, then don't use Zope for your images. You aren't gaining anything. Use an apache front end, proxy through part for Zope (using VHM) and part for the images. Stick the images on Apache and be done with it. To be really cheeky, a 302 response should be sufficient to tell the browser that /spam/images/navigation/home.gif is the same image as /images/navigation/home.gif. But that's not what your looking for.