What's needed and why?
Currently, we can set a challenge for all a site excluding some pattern.
One idea can be to enable it for specific path (for some sites, it's only used for search endpoint by example and sometimes, it's a mess to whitelist all pattern of api/resources/etc).
In addition, I tried to use an alternative (thx to IA, didn't found a way from the doc or from the /etc/nginx from bw) to be able to combine that with path+country/IP/etc but not tested now:
location /specific-path {
access_by_lua_file /usr/share/bunkerweb/core/antibot/antibot.lua;
proxy_pass $backend0;
}
Implementations ideas (optional)
- Allow to use whitelist pattern (regex) instead exclude pattern (regex)
- In long term (but can be difficult): allow to combine some conditions (like enable this feature only for request on /specific-path from specific country excluding specific IP)
Code of Conduct
What's needed and why?
Currently, we can set a challenge for all a site excluding some pattern.
One idea can be to enable it for specific path (for some sites, it's only used for search endpoint by example and sometimes, it's a mess to whitelist all pattern of api/resources/etc).
In addition, I tried to use an alternative (thx to IA, didn't found a way from the doc or from the /etc/nginx from bw) to be able to combine that with path+country/IP/etc but not tested now:
Implementations ideas (optional)
Code of Conduct