different or incorrect logging when request is blocked because of invalid content-type

[pasikarkkainen]

Sending HTTP GET request thru lua-resty-waf reverse proxy with an invalid content-type:
curl -H "Content-Type:foobar" "http://reverseproxy.domain.tld/lua-resty-waf/index.html"

.. causes the request to be blocked with HTTP 403 Forbidden, which is a correct action to do.

But in this case openresty debug error.log doesn't have the usual JSON string of why the request was blocked, because lua-resty-waf doesn't actually see this as matching a rule, because it just calls ngx.exit(ngx.HTTP_FORBIDDEN) inside of resty.waf.request.lua.

As discussed on IRC this should be fixed.

[p0pr0ck5]

Look into tying this into CRSv3 translation/setvar interface

[p0pr0ck5]

See note in #239. Targeting v0.12