Skip to content
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

Feature request (?): Share the CrowdSec response instead of redirecting #1

Open
dune73 opened this issue Nov 20, 2024 · 1 comment
Open

Comments

@dune73
Copy link

dune73 commented Nov 20, 2024

Thanks for providing this module. This is something I wanted to have for quite some time.

Yes for my needs, the module does too much. I would rather have the CrowdSec response, ideally with as much info as possible (not sure what CrowdSec is able to include in the response) and make it accessible via environment variables or some other mechanism.

That way I can consume the CrowdSec with ModSecurity (or ModRewrite) and keep the intelligence there.

Is this feasible at all for your module or something you are not interested in?

(Or do you see a way how I could use the CrowdLocation mechanism to implement the feature I described above?)

@buixor
Copy link
Collaborator

buixor commented Nov 21, 2024

Hello,

it might happen if we see some "trivial" way to do it, but to be honestly it's not our top priority (we have stream mode, appsec/waf, metrics etc. to deal with first)

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