[Bug 64661] New: Include error should not always be logged as error.

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=64661

            Bug ID: 64661
           Summary: Include error should not always be logged as error.
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_include
          Assignee: bugs@httpd.apache.org
          Reporter: apache@ohreally.nl
  Target Milestone: ---

Hello,

In my opinion, an include error in an <!--#include --> element should not be
logged as 'error' if it was resolved by an 'onerror' attribute, but rather as
'warning'. The initial error was dealt with, so it's no longer an error.

Example:

<!--#include virtual="no.shtml" --> : 'error'

<!--#include virtual="no.shtml" onerror="yes.shtml" --> : 'warning'

<!--#include virtual="no.shtml" onerror="also-no.shtml" --> : 'error'

Practical motivation: often, the 'onerror' attribute is an acceptable way to
work around non-existing files, which means they do not require my direct
attention; having them logged as errors complicates finding the real errors,
that really require my direct attention, in the log file.

Thanks for considering,
  Rob

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org