Adds missing 'ModSecurity:' prefix to log messages

As reported by Walter Hop, the status call functionality was printing a message
in the console without the expected 'ModSecurity:' prefix. SecServerSignature
was also printing messages without the expected prefix. Both are fixed by this
commit.
This commit is contained in:
Felipe Zimmerle 2014-11-28 02:12:20 -08:00
parent ce4cf24f6e
commit fe22446bdd

View File

@ -748,7 +748,8 @@ static int hook_post_config(apr_pool_t *mp, apr_pool_t *mp_log, apr_pool_t *mp_t
/* If we've changed the server signature make note of the original. */
if (new_server_signature != NULL) {
ap_log_error(APLOG_MARK, APLOG_NOTICE | APLOG_NOERRNO, 0, s,
"Original server signature: %s", real_server_signature);
"ModSecurity: Original server signature: %s",
real_server_signature);
}
#ifndef WIN32
@ -757,8 +758,8 @@ static int hook_post_config(apr_pool_t *mp, apr_pool_t *mp_log, apr_pool_t *mp_t
}
else {
ap_log_error(APLOG_MARK, APLOG_NOTICE, 0, NULL,
"Status engine is currently disabled, enable it by set " \
"SecStatusEngine to On.");
"ModSecurity: Status engine is currently disabled, enable " \
"it by set SecStatusEngine to On.");
}
#endif