diff options
| author | Jorge Lustosa <jorgelustosa@gmail.com> | 2015-12-01 13:43:15 -0200 |
|---|---|---|
| committer | Jorge Lustosa <jorgelustosa@gmail.com> | 2015-12-01 13:43:15 -0200 |
| commit | be87c91439503c1d3c810b0aa3eaf8178cfce3e4 (patch) | |
| tree | 79c532dde05f56a9f6cd42fb8a8c151ef7aa1713 | |
| parent | 043bd6b3a5d02b3aead7a982f0e86348280af20d (diff) | |
| download | pfsense-packages-be87c91439503c1d3c810b0aa3eaf8178cfce3e4.tar.gz pfsense-packages-be87c91439503c1d3c810b0aa3eaf8178cfce3e4.tar.bz2 pfsense-packages-be87c91439503c1d3c810b0aa3eaf8178cfce3e4.zip | |
AH00526: Syntax error on line 539 of /usr/pbi/proxy_mod_security-amd64/etc/apache24/httpd.conf
When you start /usr/local/etc/rc.d/apache_mod_security.sh start you receive this error.
"AH00526: Syntax error on line 539 of /usr/pbi/proxy_mod_security-amd64/etc/apache24/httpd.conf:
ModSecurity: No action id present within the rule" every rule needs a ID to work, that fix just make this.
| -rw-r--r-- | config/apache_mod_security-dev/apache_mod_security.template | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/config/apache_mod_security-dev/apache_mod_security.template b/config/apache_mod_security-dev/apache_mod_security.template index d004a9ae..107deb8b 100644 --- a/config/apache_mod_security-dev/apache_mod_security.template +++ b/config/apache_mod_security-dev/apache_mod_security.template @@ -25,7 +25,7 @@ SecRequestBodyAccess On # Initiate XML Processor in case of xml content-type # SecRule REQUEST_HEADERS:Content-Type "text/xml" \ - "phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML" + "id:20001,phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML" # Maximum request body size we will accept for buffering. If you support @@ -56,7 +56,7 @@ SecRequestBodyLimitAction Reject # or log a high-severity alert (when deployed in detection-only mode). # SecRule REQBODY_ERROR "!@eq 0" \ -"phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2" +"id:20002,phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2" # By default be strict with what we accept in the multipart/form-data # request body. If the rule below proves to be too strict for your @@ -64,7 +64,7 @@ SecRule REQBODY_ERROR "!@eq 0" \ # _not_ to remove it altogether. # SecRule MULTIPART_STRICT_ERROR "!@eq 0" \ -"phase:2,t:none,log,deny,status:44,msg:'Multipart request body \ +"id:20003,phase:2,t:none,log,deny,status:44,msg:'Multipart request body \ failed strict validation: \ PE %{REQBODY_PROCESSOR_ERROR}, \ BQ %{MULTIPART_BOUNDARY_QUOTED}, \ @@ -81,7 +81,7 @@ IH %{MULTIPART_FILE_LIMIT_EXCEEDED}'" # Did we see anything that might be a boundary? # SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \ -"phase:2,t:none,log,deny,status:44,msg:'Multipart parser detected a possible unmatched boundary.'" +"id:20004,phase:2,t:none,log,deny,status:44,msg:'Multipart parser detected a possible unmatched boundary.'" # PCRE Tuning # We want to avoid a potential RegEx DoS condition |