DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41963>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41963 Summary: PATCH: Enhancement to mod_expires to allow "expire in X seconds if file is at least Y seconds old" Product: Apache httpd-1.3 Version: HEAD Platform: All OS/Version: other Status: NEW Severity: normal Priority: P5 Component: Other mods AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Some shy away from setting an expire time on images because they often update images in place, particularly recently-created images. This addition to mod_expire addresses the latter case, allowing one to set different expire times depending on whether the file being served is/isn't older than some set threshold. For example, to set the expire time far into the future for JPG files that are more than a week old: ExpiresByType image/jpeg "aged 1 week then 10 years" This leaves JPG images less than a week old without an expire tag, and ones a week old or older with one 10 years in the distance (from the access time). It also supports an "else" clause: ExpireByType image/jpeg "aged 1 week then 10 years else 1 hour" The patch does not include the documentation -- I wanted to gauge the reaction, first. This small patch can go a long way toward allowing web sites to get the benefits of image caching, while still allowing a window for in-place updates. This can also be useful for CSS and JS, in conjunction with filename versioning. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
