Bug 64661 - Include error should not always be logged as error.
Summary: Include error should not always be logged as error.
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_include (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-11 14:47 UTC by Rob
Modified: 2020-08-11 14:47 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob 2020-08-11 14:47:23 UTC
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