owasp-modsecurity / owasp-modsecurity/ModSecurity
Hit rule and record request_body log.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Can ModSecurity v3 pass relevant environment variables to Nginx for judgment?
For example, nginx access_log request_body defaults to empty, and when a WAF rule is hit, access_log will record the value of request_body.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ModSecurity v3 integration with Nginx and how Nginx access_log handles request_body. Determine whether relevant environment variables can be exposed when a WAF rule is hit, then verify that the resulting access log contains the request body for that case. The issue names no specific files or tests, so the integration points and test approach need to be identified first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nginx
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100