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.

Sign up for GitHub

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

Jump to bottom

Mislabeled environment variables #320

Closed
50tonrobot opened this issue Jan 10, 2025 · 1 comment · Fixed by #321
Closed

Mislabeled environment variables #320

50tonrobot opened this issue Jan 10, 2025 · 1 comment · Fixed by #321

Comments

@50tonrobot
Copy link

50tonrobot commented Jan 10, 2025 •
edited
Loading

Sorry I know I am probably not using the correct format here for reporting an issue. But I found that the README.md documentation has a couple of incorrect environment variable labels.

I am using the docker container: owasp/modsecurity-crs:nginx

ANOMALY_INBOUND doesn’t work, INBOUND_ANOMALY does.
ANOMALY_OUTBOUND doesn’t work, OUTBOUND_ANOMALY does.
@franbuehler
Copy link
Contributor

Thank you for the report.
You're right, in this file (and it's the only one, but important) the variable names INBOUND_ANOMALY and OUTBOUND_ANOMALY are used:
https://github.com/coreruleset/modsecurity-crs-docker/blob/main/src/opt/modsecurity/configure-rules.conf#L13

@franbuehler franbuehler mentioned this issue Jan 10, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: set correct variable names for ANOMALY_INBOUND and OUTBOUND franbuehler/modsecurity-crs-docker
2 participants
@50tonrobot @franbuehler