-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add AppSec
integration
#57
Conversation
AppSec
integrationAppSec
integration
this will probably require some update to documentation, too. At least I'd expect it to require some extra setup, that should be documented. |
Absolutely. I've already prepared something in e50ba57. Main changes are addition of the In addition to that I've removed the (full) JSON configuration, because support fort the |
This commit ensures that responses from the CrowdSec `AppSec` remediation component are properly evaluated and acted upon. The `AppSec` support can be enabled either as a dedicated handler by configuring a route to have the `appsec` directive. That will use the `http.handlers.appsec` module. It also enables `AppSec` checks on the the HTTP handler configured through the `crowdsec` directive using the `http.handlers.crowdsec` module by default. In a future commit `AppSec` support will be enabled based on configuration on the `http.handlers.crowdsec` component.
This commit explicitly sets the content length of the request, so that CrowdSec actually reads the request body, instead of skipping it. Two new tests that involve an HTTP request body have been added as integration tests.
No description provided.