Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blocked requests in SIMULATE mode if not in allowed_content_types #239

Open
pasikarkkainen opened this issue Nov 8, 2016 · 2 comments
Open
Assignees
Labels
Milestone

Comments

@pasikarkkainen
Copy link

It seems lua-resty-waf can block requests even in SIMULATE mode, which was a bit surprising.

If request content-type isn't listed in "allowed_content_types" setting, lua-resty-waf will block the request, even in SIMULATE mode.

Also I couldn't find a log entry about the blocked request, or the reason why it was blocked.

Something wrong in my settings, or is this a bug?

Thanks!

@p0pr0ck5
Copy link
Owner

p0pr0ck5 commented Nov 9, 2016

Hi,

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

@p0pr0ck5 p0pr0ck5 added this to the v0.9 milestone Nov 9, 2016
@p0pr0ck5 p0pr0ck5 added the bug label Nov 9, 2016
@p0pr0ck5 p0pr0ck5 self-assigned this Nov 9, 2016
@p0pr0ck5 p0pr0ck5 removed this from the v0.9 milestone Jan 25, 2017
@p0pr0ck5
Copy link
Owner

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 module option in the release following the upcoming v0.11 release, and remove this entirely by v1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants