RESPONSE_BODY not work when using proxy_module

[friparia]

Original Issue: owasp-modsecurity/ModSecurity#1520

The reason is that when using proxy, variable buffer_fully_loadead cannot be assigned to 1, so it cannot execute the modsecurity functions.

In my project, I just delete this variable and it works fine with me, but I don't know whether it has the side effect or some other bugs.

[azurit]

I'm not able to match RESPONSE_BODY even using ctl:ruleRemoveTargetById (so it cannot be excluded).

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[Sodium-Hydrogen]

Any progress on this?

[Sodium-Hydrogen]

For anyone else who runs into this. Nginx as a proxy with modsecurity was working I just didn't have the correct mime type set so it looked like it wasn't working.

[amsnek]

hmm response body seems to be processed, modsecurity claims to throw 403 but requests gets through? i assume this wont be fixed anymore?
@Sodium-Hydrogen what did you mean it worked for you but mime type was not set? for me, php leakage gets through to client with 5xx -> the mime type on response seems correct though 🤔
modsecurity even logs 403 but that is not accurate

edit: never mind -> proxy_buffering was off in nginx