Robert comments

Results 69 comments of


                                            Robert

Streaming multipart/form-data request body via http v2 not supported yet

Renaming the title of this issue for clarification.

Streaming multipart/form-data request body via http v2 not supported yet

Noting here for posterity, this links more closely to https://github.com/openresty/lua-resty-upload/issues/24 than other issues note above, as we leverage this library directly.

Streaming multipart/form-data request body via http v2 not supported yet

Unless lua-resty-upload has started supporting HTTP/2, then no ;)

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

Look into tying this into CRSv3 translation/setvar interface

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

See note in #239. Targeting v0.12

Implement ctl nondisruptive actions

Started with straight ID removal in https://github.com/p0pr0ck5/lua-resty-waf/commit/6205c3850eb9796d34227c3e92810d6e7e2a74af

Implement ctl nondisruptive actions

ctl:ruleEngine was done in https://github.com/p0pr0ck5/lua-resty-waf/commit/94a6563a5dbc57622761fdf379d740d93021b0e1

blocked requests in SIMULATE mode if not in allowed_content_types

Hi, Thanks for the report. This is very similar to #232 and will be handled in that patch set.

blocked requests in SIMULATE mode if not in allowed_content_types

These module options will likely go away in favor of direct SecRules translation, made much more consumable by the addition of the `setvar` module API. Planning refactor and deprecate this...

Please improve documentation

Hi, **Section Synopsis: explain what the effect is of calling waf:exec() in all of access_by_lua, header_filter_by_lua and body_filter_by_lua. why do you need to call waf:exec() in each of them?** Calling...