Skip to content

where did acl 80005 (disabled_extensions) go? #303

Answered by tinselcity
at1984z asked this question in Q&A
Discussion options

You must be logged in to vote

We moved the access control lists into their own "entity" type which takes it's own json that can be loaded in a similar fashion to the waf profiles.

Here's an example using waflz_server (utility server built with waflz)

Here's a basic acl config (json) with just one extension blocked:

{
  "disallowed_extensions": [
    ".xxx"
  ]
}

Running waflz_server (listening on port 12345) from the build dir:

~/gproj/waflz/build>./util/waflz_server/waflz_server --port 12345 --acl ./my_cool_acl.json
...

Then curl ing from another terminal

~>curl -s localhost:12345/index.xxx | jq '.'
{
  "rule_msg": "File extension is not allowed by policy",
  "sub_event": [
    {
      "rule_id": 80005,
      "rule_msg"

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by at1984z
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants