DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26731>. 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: [email protected] ReportedBy: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
