I'm not sure if the plugin is causing this, or if it's the owasp container. That's why I opened the same issue on the owasp container: coreruleset/modsecurity-crs-docker#85
I have a form which submits base64 images, so the request body size is somewhere in the 8Mb.
On the owasp container, If I don't specify MODSEC_REQ_BODY_NOFILES_LIMIT with a big number, then I will see the modsec rule 200002 to fire.
If I specify MODSEC_REQ_BODY_NOFILES_LIMIT with a big enough number (25Mb in my case), the modsec container will not show any errors, however my page will display a 500 Internal Server Error.
If I don't use modsec at all, my page does not show any error.
Would anyone have a clue why this is happening?
To be clear, I'm not uploading files, just big text body content.
The reason I'm also posting here, is because the rule will correctly fire if I leave its default value of 128Kb. So I assume it can correctly handle such big request body. So if it can handle it, it must fail somewhere else I would guess.
And when the rule correctly fires, I still see a 500 error on my webpage, so I assume there is still something wrong going on somewhere
I am using the plugin in its version 1.2.1, with maxBodySize: 26214400
I also tried version 1.1.0 with the same result
I'm not sure if the plugin is causing this, or if it's the owasp container. That's why I opened the same issue on the owasp container: coreruleset/modsecurity-crs-docker#85
I have a form which submits base64 images, so the request body size is somewhere in the 8Mb.
On the owasp container, If I don't specify
MODSEC_REQ_BODY_NOFILES_LIMITwith a big number, then I will see the modsec rule200002to fire.If I specify
MODSEC_REQ_BODY_NOFILES_LIMITwith a big enough number (25Mb in my case), the modsec container will not show any errors, however my page will display a500 Internal Server Error.If I don't use modsec at all, my page does not show any error.
Would anyone have a clue why this is happening?
To be clear, I'm not uploading files, just big text body content.
The reason I'm also posting here, is because the rule will correctly fire if I leave its default value of 128Kb. So I assume it can correctly handle such big request body. So if it can handle it, it must fail somewhere else I would guess.
And when the rule correctly fires, I still see a 500 error on my webpage, so I assume there is still something wrong going on somewhere
I am using the plugin in its version 1.2.1, with maxBodySize: 26214400
I also tried version 1.1.0 with the same result