Minor fix in the decision on whenever the log callback should be called

This commit is contained in:
Felipe Zimmerle 2017-02-26 02:07:14 -03:00
parent e2af60e765
commit e79712095b
No known key found for this signature in database
GPG Key ID: E6DFB08CE8B11277
3 changed files with 3 additions and 4 deletions

View File

@ -52,7 +52,7 @@ class RuleMessage {
m_ruleFile(rule->m_fileName),
m_ruleId(rule->m_ruleId),
m_ruleLine(rule->m_lineNumber),
m_saveMessage(false),
m_saveMessage(true),
m_serverIpAddress(trans->m_serverIpAddress),
m_severity(0),
m_uriNoQueryStringDecoded(trans->m_uri_no_query_string_decoded),

View File

@ -697,7 +697,7 @@ end_clean:
end_exec:
executeActionsAfterFullMatch(trans, containsDisruptive, ruleMessage);
if (this->m_chained == false) {
if (this->m_chained == false && ruleMessage->m_saveMessage != false) {
trans->serverLog(ruleMessage);
trans->m_rulesMessages.push_back(*ruleMessage);
}

View File

@ -100,8 +100,7 @@ std::string RuleMessage::errorLog(const RuleMessage *rm) {
}
std::string RuleMessage::log(const RuleMessage *rm) {
std::string msg;
std::string msg("");
if (rm->m_isDisruptive) {
msg.append(disruptiveErrorLog(rm));
} else {