https://bz.apache.org/bugzilla/show_bug.cgi?id=59612
Bug ID: 59612
Summary: Follow the convention of logging "require" directives
in mod_authz_host upon expr evaluation failure
Product: Apache httpd-2
Version: 2.4.20
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_authz_host
Assignee: [email protected]
Reporter: [email protected]
In authz modules, when the require expression cannot be evaluated, the log
files prints the "require" directive, an excellent practice!!
authz_host authorize: require host: Can't evaluate require expression: %s"
authz_dbd authorize: require dbd-group: Can't evaluate require expression: %s
authz_dbm authorize: require dbm-group: Can't evaluate require expression: %s"
authz_user authorize: require user: Can't evaluate require expression: %s"
authz_groupfile authorize: require group: Can't evaluate require expression:
%s"
auth_ldap authorize: require dn: Can't evaluate expression: %s
auth_ldap authorize: require group: Can't evaluate expression: %s
auth_ldap authorize: require ldap-attribute: Can't evaluate expression: %s
auth_ldap authorize: require ldap-filter: Can't evaluate require expression: %s
auth_ldap authorize: require user: Can't evaluate expression: %s
auth_ldap authorize: require ldap-search: Can't evaluate require expression: %s
But in forward_dns_check_authorization(..) in mod_authz_host.c, the convention
is somehow not followed, with the following msg:
Can't evaluate require expression: %s
Let's add the require directive for the ease of debugging (see the attached
patch).
ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, APLOGNO(03354)
+ "authz_host authorize: require forward-dns: "
"Can't evaluate require expression: %s", err);
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]