corazawaf/coraza

docs: investigate RESPONSE_CONTENT_LENGTH variable

Open

#1,566 opened on Mar 22, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (333 forks)auto 404
documentationgood first issue

Repository metrics

Stars
 (3,627 stars)
PR merge metrics
 (PR metrics pending)

Description

  1. why is it named "content" and not aligned the the request body variable RequestBodyLength? Should we create an alias?
  2. when is it populated? Looks like it is populated only when no response body processor is active. Is it correct? Is it aligned with ResponseBody?
  3. Does forceResponseBodyVariable have some implications on ResponseContentLength?

From https://github.com/corazawaf/coraza/pull/1565.

Contributor guide

Research direction
Investigate the RESPONSE CONTENT LENGTH variable in Coraza: clarify its naming inconsistency with RequestBodyLength, conditions under which it is populated, and the effect of forceResponseBodyVariable on it.
Tech stack
go
Domain
backendsecurity
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55