Published 10 months ago
Published 10 months ago
Peter Larin
Updated 10 months ago
0
In HTTP Flood - Access limiting:
Carrie
Updated 10 months ago
0
Could you please test it with other IPs?
After clearing the cache, does the anti-bot challenge page appear on the first request?
Is it possible that the token hasn’t expired, so the requests continue without triggering the challenge?
The anti-bot challenge does not appear on every request — once it has been passed, it won’t trigger again until the token expires.
Peter Larin
Updated 10 months ago
0
Hi! To be clear, the antibot feature appears in 2 places: HTTP FLOOD and ANTIBOT. I have ANTIBOT switched off. I expect that Antibot screen will appear as a result of Http Flood hitting the threshold (there are 2 options - Block and Challenge).
Summary: the Antibot screen does appear when ANTIBOT heature is enabled (on the 1st request as you said), BUT the antibot screen does not appear when HTTP FLOOD feature + Challenge is enabled.
Carrie
Updated 10 months ago
Peter Larin
Updated 10 months ago
0
As i discovered, if i trigger the HTTP flood in browser, there's no antibot in browser. However if I trigger antibot with tools like curl, I do receive antibot status code to curl requests. I'm not sure if this is by design. It makes sense though.
Carrie
Updated 10 months ago
SafeLine’s Anti-Bot works by analyzing browser features and behavior, so real browsers may pass, while tools like curl lack these traits and may be challenged
Chris Couture
Updated 10 months ago
Makes sense. I had the same question when testing with a browser. Was busy with other things so didn't bother to test more or raise a ticket.