Skip to content

SecRequestBodyLimitAction ProcessPartial truncated POST data for mod_proxy when the SecRequestBodyLimit is exceeded #406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rcbarnett-zz opened this issue Oct 17, 2013 · 2 comments
Assignees

Comments

@rcbarnett-zz
Copy link
Contributor

MODSEC-252: Config:

SecRuleEngine DetectionOnly
SecRequestBodyAccess On
SecRequestBodyLimit 10

Result with big POST:

proxy host:
[Tue Jun 07 10:40:51 2011] [error] [client a.b.c.d] ModSecurity: Request body (Content-Length) is larger than the configured limit (10). [hostname "test"] [uri "/test"] [unique_id "Te3kEwoNzNMAACBtAX0AAAAA"]

the request is then passed to the mod_proxy_balancer and to the another host (HTTP Backend) but the application on that hosts gets corrupted data - data is truncated to the SecRequestBodyLimit.

I've also tried setting "SecRuleEngine On" with "SecRequestBodyLimitAction ProcessPartial" but the result is the same - proxied POST data is corrupted.

Removing SecRuleEngine from the configuration couses proxying without any problems.

I'd like to add that low SecRequestBodyLimit is essential for me.

@rcbarnett-zz
Copy link
Contributor Author

Original reporter: pkoper

@rcbarnett-zz
Copy link
Contributor Author

bpinto: Let me debug it a little bit more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants