parser: SecRequestBodyInMemoryLimit is now returning an error msg

This commit is contained in:
Felipe Zimmerle 2017-08-22 10:42:47 -03:00
parent 2cf636cf76
commit 81879cd131
No known key found for this signature in database
GPG Key ID: E6DFB08CE8B11277
3 changed files with 573 additions and 566 deletions

View File

@ -451,7 +451,6 @@ class RulesProperties {
ConfigBoolean m_secXMLExternalEntity;
ConfigBoolean m_tmpSaveUploadedFiles;
ConfigBoolean m_uploadKeepFiles;
ConfigDouble m_requestBodyInMemoryLimit;
ConfigDouble m_requestBodyLimit;
ConfigDouble m_requestBodyNoFilesLimit;
ConfigDouble m_responseBodyLimit;

File diff suppressed because it is too large Load Diff

View File

@ -1370,8 +1370,12 @@ expression:
}
| CONFIG_DIR_REQ_BODY_IN_MEMORY_LIMIT
{
driver.m_requestBodyInMemoryLimit.m_set = true;
driver.m_requestBodyInMemoryLimit.m_value = atoi($1.c_str());
std::stringstream ss;
ss << "As of ModSecurity version 3.0, SecRequestBodyInMemoryLimit is no longer ";
ss << "supported. Instead, you can use your web server configurations to control ";
ss << "those values. ModSecurity will follow the web server decision.";
driver.error(@0, ss.str());
YYERROR;
}
| CONFIG_DIR_RES_BODY_LIMIT
{