Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Review usage of tx.0

See original GitHub issue

_Issue originally created by user fgsch on date 2018-06-06 16:39:01. Link to original issue: https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1121._

We have many rules (grep says 140) using something along this line:

setvar:'tx.%{rule.id}-OWASP_CRS/LEAKAGE/ERRORS-%{matched_var_name}=%{tx.0}'

As found by dune73 in #1107, %{matched_var} would be a better fit. There is also the question about how useful this is.

Issue Analytics

State:
Created 3 years ago
Comments:6

Top GitHub Comments

1reaction

CRS-migration-botcommented, May 13, 2020

User fgsch commented on date 2019-03-18 14:32:09:

PR opened

1reaction

CRS-migration-botcommented, May 13, 2020

User dune73 commented on date 2019-03-08 21:49:03:

I’m not a fan of this construct and I have played around with removing this altogether. It was needed in a special construct in 949xxx in former versions, but that construct is gone and I think we could kick it together with the setvar:'tx.msg=%{rule.msg}' construct (the latter is used in 980xxx).

Thoughts?

CC csanders-git, lifeforms