wiki: Remove deprecated REQBODY_PROCESSOR_ERROR and REQBODY_PROCESSOR_ERROR_MSG from wiki pages #3576
Description
Activity
Hi @hnakamur,
probably you're right. But we have to investigate the current behavior, it seems like those variables are still in use, see this part.
(I just took a quick look, but may be the logic is wrong there, because if the
error.empty()is false, then transactions sets those variables, but if it's empty, then it resets theREQBODY_ERRORvariable. And only that one.)@dune73 do you have any idea why they made these mentioned variables deprecated? It seems like it was a name change...
Hi @airween,
Yes, it is still in use in v3, but not in v2. So I think we would deprecate them in v3 too.Hi @airween, Yes, it is still in use in v3, but not in v2. So I think we would deprecate them in v3 too.
I've been working on v4, first PR's will arrive soon. May be we should remove them there.
Reacted by Hiroaki Nakamura- added2.xRelated to ModSecurity version 2.xRelated to ModSecurity version 2.x
on Jun 16, 2026 Hi @airween,
Thank you for pointing out that
REQBODY_PROCESSOR_ERRORandREQBODY_PROCESSOR_ERROR_MSGare still used in v2.However their values are always the same as new
REQBODY_ERRORandREQBODY_ERROR_MSGrespectively since theREQBODY_PROCESSOR_ERRORandREQBODY_ERRORshare the same variable generation function. The same is true forREQBODY_PROCESSOR_ERROR_MSGandREQBODY_ERROR_MSG.Therefore, we can simply use
REQBODY_ERRORandREQBODY_ERROR_MSGinstead ofREQBODY_PROCESSOR_ERRORandREQBODY_PROCESSOR_ERROR_MSG.I searched for
REQBODY_PROCESSOR_ERRORin the coreruleset repository:https://github.com/search?q=repo%3Acoreruleset%2Fcoreruleset%20REQBODY_PROCESSOR_ERROR&type=code
There is only one occurrence, in CHANGES.md, so there are no actual references to
REQBODY_PROCESSOR_ERRORorREQBODY_PROCESSOR_ERROR_MSGin the rules themselves.So I agree that we should remove
REQBODY_PROCESSOR_ERRORandREQBODY_PROCESSOR_ERROR_MSG, and I've opened a PR: #3578I am also trying to create a PR for v3:
a22fd2eHowever, I don't know how to update
src/parser/seclang-parser.ccafter modifyingsrc/parser/seclang-parser.yy.
I expected it to be regenerated by running make, but it wasn't (please see the ls -l src/parser output in the commit message).Reacted by Ervin HegedusI updated
src/parser/seclang-parser.ccby hand and opened a PR for v3: #3579However, I don't know how to update
src/parser/seclang-parser.ccafter modifyingsrc/parser/seclang-parser.yy.After you changed the lexer (
.ll) and syntax checker (.yy) files, you should run./configure --enable-parser-generation ....This will generate
src/parser/seclang-parser.cc,src/parser/seclang-parser.hh,src/parser/seclang-scanner.ccand other necessary files. Then you can add them to the commit.- added a commit that references this issue
on Jul 2, 2026
I found that
REQBODY_PROCESSOR_ERRORandREQBODY_PROCESSOR_ERROR_MSGwere deprecated in this commit:d0e2546
It appears that these variables have not been assigned any values in the v2/master branch since then.
Therefore, I think we should either remove
REQBODY_PROCESSOR_ERRORandREQBODY_PROCESSOR_ERROR_MSGfrom the v2 wiki pages or add a note explaining that they are deprecated.I also think they should be removed from the v3 wiki pages.