Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 58400 invoked from network); 6 Feb 2004 16:37:10 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Feb 2004 16:37:10 -0000 Received: (qmail 96296 invoked by uid 500); 6 Feb 2004 16:37:01 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 96260 invoked by uid 500); 6 Feb 2004 16:37:01 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 96235 invoked from network); 6 Feb 2004 16:37:01 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 6 Feb 2004 16:37:01 -0000 Received: (qmail 23195 invoked by uid 50); 6 Feb 2004 16:37:19 -0000 Date: 6 Feb 2004 16:37:19 -0000 Message-ID: <20040206163719.23194.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 26731] New: - mod_proxy won't cache if last-modified is missing, even if Expires: is valid X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26731 mod_proxy won't cache if last-modified is missing, even if Expires: is valid Summary: mod_proxy won't cache if last-modified is missing, even if Expires: is valid Product: Apache httpd-1.3 Version: 1.3.29 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: mod_proxy AssignedTo: bugs@httpd.apache.org ReportedBy: boutell@boutell.com There is a straightforward fix for this. Apologies for the informal patch, but you'll find it in mod_cache.c right away by searching for the line before my "TBB" comment. The last line below is the actual code change. With this simple modification, mod_expires can be used on a back-end server in conjunction with mod_proxy on the front end server to greatly reduce load on the back end for URLs that aren't obviously static (but the designer knows they are and has chosen to use mod_expires, which mod_proxy ought to honor). Thanks. /* * 200 OK response from HTTP/1.0 and up without a Last-Modified header * TBB 02/06/04: an Expires header is also acceptable. */ (r->status == HTTP_OK && ((lmods == NULL) && (expire == NULL)) && is_HTTP1) || --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org