I had been using the following directives with Apache 1.3.27: ExpiresActive On ExpiresByType image/gif A5184000 ExpiresByType image/jpeg A5184000 When I upgraded to Apache 2.0.47, I began getting entries such as these in my error_log: [Sat Oct 11 16:02:54 2003] [error] [client w.x.y.z] internal error: bad expires code: /foo/bar/index.html [Sat Oct 11 16:10:44 2003] [error] [client w.x.y.z] internal error: bad expires code: /foo/bar/all.txt These errors occur whenever there should be no Expires header (since no ExpiresByType matches and no ExpiresDefault is specified). With Apache 1.3.27, no such errors occurred. In case it's relevant, I'm using Linux x86, kernel 2.2.19.
Created attachment 8538 [details] Patch to eliminate the error
Hmm. I think, the right fix would be to set new->expiresdefault = NULL in create_dir_expires_config and to change the merger accordingly. Your fix seems to be just a work around. Thanks for the report and thanks for using Apache!
Created attachment 8544 [details] Alternate patch that uses NULL for expiresdefault
enabling the PatchAvailable keyword updated doc on submitting patches is at http://httpd.apache.org/dev/patches.html
*** Bug 24459 has been marked as a duplicate of this bug. ***
I have tested and committed this patch to the 2.1-dev branch of Apache and submitted it for a vote for backporting into the 2.0 stable branch. Thank you for using Apache and for taking the time to track down a fix and submit a patch.
*** Bug 21907 has been marked as a duplicate of this bug. ***