Configuration to challenge all requests #76
insanitywholesale
started this conversation in
General
Replies: 2 comments
-
Perhaps misconfiguration, after adding |
Beta Was this translation helpful? Give feedback.
0 replies
-
Probably need to add a warning in the logs if you haven't specified a bot policy configuration. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm not sure if this is a misunderstanding or misconfiguration on my part so I didn't want to open a potentially incorrect issue.
My goal is to challenge all requests no matter the user agent, path or address they have. Of course if the client has solved the challenge once, it should be let through without solving it again but on initial request I'd like the challenge to be required for everyone.
I tried to add a policy using the "everything" value for each of them and even all of them together:
This still allows a request with
curl
to get through.My setup is a modified version of the example
docker-compose.yml
, I just changed the port to 8090 and moved the botPolicy.json bind mount to the anubis container and changed the container names:Is there a way to achieve this, am I missing something or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions