You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/10/11 22:19:16 UTC

DO NOT REPLY [Bug 23748] New: - "internal error: bad expires code" if expires criteria aren't met

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=23748>.
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=23748

"internal error: bad expires code" if expires criteria aren't met

           Summary: "internal error: bad expires code" if expires criteria
                    aren't met
           Product: Apache httpd-2.0
           Version: 2.0.47
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_expires
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: liam@htmlhelp.com


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org