Skip to content

Implement the support for "SecDisableBackendCompression" directive in libModSecurity #1470

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
victorhora opened this issue Jun 23, 2017 · 3 comments

Comments

@victorhora
Copy link
Contributor

The support for "SecDisableBackendCompression" is not yet implemented.

Further information about this directive available here:
https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#SecDisableBackendCompression

@victorhora victorhora changed the title Implement the support for "SecDisableBackendCompression" action in libModSecurity Implement the support for "SecDisableBackendCompression" directive in libModSecurity Jun 23, 2017
@victorhora
Copy link
Contributor Author

It was realized that this feature should not be implemented in libModSecurity core but rather on the connectors if due necessary.

@zoltan-fedor
Copy link

Sorry for commenting on the closed issue, but are there any timelines on this being implemented?
Without this, libModSecurity is pretty much useless in a reverse proxy mode - as you either need to turn off compression both on the backend and the front (which you can't do in production) or turn off response body inspection (which is then a major security risk).

@zimmerle
Copy link
Contributor

zimmerle commented May 8, 2018

@zoltan-fedor the compression can be disabled in the web server configuration, regardless of ModSecurity utilization.

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

No branches or pull requests

3 participants