Hi Francois, I've already sent a POST regarding the mod_mem_cache usage. http://httpd.markmail.org/search/?q=paillart#query:paillart+page:1+mid:bws5recajzhtqc7k+state:results >From my point of view, this module is not really usable. I've benchmarked the mod_disk_cache module and found same results as for mod_mem_cache in my use case (download iso files). So the best way is to use this cache implementation. Thanks to the sendfile mechanism !!! Because your clients don't send conditional Headers,
it will receive always the whole content. 3. You set both the Expires and Cache-Control:max-age
headers. According to the HTTP/1.1 specifications :"The max-age directive takes priority over Expires, so if max-age is
present in a response, the calculation is simply: So only the Cache-Control:max-age header (300) will be taken into
account. According to the HTTP/1.1 specifications : "Also, if the response does have a Last-Modified time, the heuristic
expiration value SHOULD be no more than some fraction of the interval
since that time. A typical setting of this fraction might be 10%. response_is_fresh = (freshness_lifetime > current_age)" From my point of view, your content is already deprecated, so it
will not be cached. Bye |
begin:vcard fn:Frederic Paillart n:Paillart;Frederic org:gemalto;WSDS adr:ZI Athelia IV;;La Vigie;La Ciotat;;13705;France email;internet:[EMAIL PROTECTED] title:Development Engineer tel;work:04 42 36 43 38 tel;fax:04 42 36 32 00 x-mozilla-html:TRUE url:http://www.gemalto.com version:2.1 end:vcard
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]