Apache error 500 on large file uploads (mod_security)
Solution 1
The fact you have a ModSecurity alert
means that you can't have empty activated_rules folder or you are including the rules in some other way.
There are known problems with ModSecurity for this error and it seems very susceptible to false positives.
The main advice when I rule is raising too many false positives is to just turn off that rule (I'm assuming it's rule 200003 that's firing but replace the id as appropriate):
SecRuleRemoveById 200003
Solution 2
I got the same error:
ModSecurity: Access denied with code 44 (phase 2). Match of "eq 0" against "MULTIPART_UNMATCHED_BOUNDARY" required. [file "/etc/httpd/conf.d/mod_security.conf"] [line "34"] [id "200003"] [msg "Multipart parser detected a possible unmatched boundary."]
But @nilpo answer was correct I got this issue due to the image name and after changing the name issue solved.
But it's not something I want because I know the solution but my customer did't know that they have to change the name.
![Octal](https://i.stack.imgur.com/u3h2q.png?s=256&g=1)
Octal
Updated on February 10, 2021Comments
-
Octal over 3 years
As far as I've tried, none of the usual solutions works for me. Well, my problem, I'm receiving an 500 Error every time I upload a "large file" (600 KB ~), with smaller images it works fine. So..., even with this (extreme) .htaccess file it keeps happening, and yes, .htaccess are active:
upload_max_filesize = 100M post_max_size = 100M memory_limit = 128M max_input_time = 6000 max_execution_time = 6000
So, I take a look at the logs and find this (is only one line, just pasted it as easy to read with line jumps):
[Mon Jul 27 17:09:28.<port> 2015] [:error] [pid 21423] [client <ip>] ModSecurity: Access denied with code 44 (phase 2). Match of "eq 0" against "MULTIPART_UNMATCHED_BOUNDARY" required. [file "/etc/httpd/conf.d/mod_security.conf"] [line "35"] [id "<another id>"] [msg "Multipart parser detected a possible unmatched boundary."] [hostname "<my host>"] [uri "<my script>"] [unique_id "<id (useless I think)"]
But, now I not able to find how to edit the mod_security (it has the default config, and empty activated_rules) config in order (i think) to allow this "large" file uploads. I'm running PHP 5.3 in Apache 2.4/CentOS 7.
-
Octal almost 9 years3600, but the page return the error 500 in almost 700 ms.
-
Octal almost 9 yearsAdded both rules (I applied 2 MB), but it keeps returning 500.
-
Barry Pollard almost 9 yearsDid you restart Apache to pick up these changes? Was it rule id 960915 which was firing? Did you add the remove code to the config AFTER the config where rule 970915 was defined and not before?
-
Octal almost 9 yearsYes, I'm restarting apache everytime. Don't know where rule 960915 is being "stored" i just pasted the line at the end.
-
Barry Pollard almost 9 yearsOk but you removed the ID when you pasted it so not sure if it is 960915. You need to go through your Apache config and see how and when the rules are being loaded.
-
Octal almost 9 yearsOk, I found this line SecRule MULTIPART_STRICT_ERROR "!@eq 0" \ "id:'<the id>',phase:2,t:none,log,deny,status:44,msg:'Multipart request body \ failed strict validation, and used your removeByID of that id, but it persists.
-
Ross Presser almost 8 yearsThis answer does not apply to this error message. The filename is not at issue.
-
Byron70 over 4 yearsI'm not sure how this is an accepted answer for the OPs upload issue. Should it not be
SecRequestBodyLimit
that should be updated for an upload issue? The default is 12.5MB.