Re: [Zope-dev] Re: How to make Zope fail nicely under high load?
Tres Seaver wrote: Bjorn Stabell wrote: If you run Apache as a caching reverse proxy (caching surrogate server) then images will be served from Apache. Only the dynamic HTML pages are served from Zope, so having them fail without regards to sessions is relatively okay. Images and other static content are almost guaranteed to load correctly, and if they didn't, a straight reload from the client will not reload cached images. Impatient clients often force reloads; I don't *think* Apache has a knob which allows a surrogate / acceloerator proxy to ignore the spec (which is written assuming forward proxies), and serve from cache anyway. I think I did find some sort of knob for this For Apache 2.0, mod_cache, dir. CacheIgnoreCacheControl could be used for this http://httpd.apache.org/docs-2.0/mod/mod_cache.html For Apache 1.3 mod_proxy, dir. CacheMaxExpire could do http://httpd.apache.org/docs/mod/mod_proxy.html#cachemaxexpire - peter. Tres. smime.p7s Description: S/MIME Cryptographic Signature ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: How to make Zope fail nicely under high load?
Peter Sabaini wrote: Tres Seaver wrote: Bjorn Stabell wrote: If you run Apache as a caching reverse proxy (caching surrogate server) then images will be served from Apache. Only the dynamic HTML pages are served from Zope, so having them fail without regards to sessions is relatively okay. Images and other static content are almost guaranteed to load correctly, and if they didn't, a straight reload from the client will not reload cached images. Impatient clients often force reloads; I don't *think* Apache has a knob which allows a surrogate / acceloerator proxy to ignore the spec (which is written assuming forward proxies), and serve from cache anyway. I think I did find some sort of knob for this For Apache 2.0, mod_cache, dir. CacheIgnoreCacheControl could be used for this http://httpd.apache.org/docs-2.0/mod/mod_cache.html For Apache 1.3 mod_proxy, dir. CacheMaxExpire could do http://httpd.apache.org/docs/mod/mod_proxy.html#cachemaxexpire Cool. I didn't remember that, and haven't been using Apache for caching for some while now. Thanks for the correction! Tres.. -- === Tres Seaver[EMAIL PROTECTED] Zope Corporation Zope Dealers http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: How to make Zope fail nicely under high load?
Bjorn Stabell wrote: Hi Peter, I think I did find some sort of knob for this For Apache 2.0, mod_cache, dir. CacheIgnoreCacheControl could be used for this http://httpd.apache.org/docs-2.0/mod/mod_cache.html For Apache 1.3 mod_proxy, dir. CacheMaxExpire could do http://httpd.apache.org/docs/mod/mod_proxy.html#cachemaxexpire I think this will force Apache to cache content no matter if the content's headers have cache control settings, but will it force Apache to not re-request the content if the browser forces a reload? (Ctrl-refresh in IE.) This really should be tested, but as far as I can remember it did serve from cache rather than rerequest. Its been some time since I did this (and at another company) and unfortunately I cant remember this too clearly... From the 'CacheIgnoreCacheControl' at least it does sound like it would ignore the spec and serve cached content though. cheers, peter. smime.p7s Description: S/MIME Cryptographic Signature ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
