0 views collected around this technical thread.
This article explains three PHP‑based techniques—captcha verification, encrypted parameter transmission, and dynamic token validation—to protect web login pages from automated crawling and credential‑stealing attacks, while also noting their limitations and implementation details.
The article presents kk-anti-reptile, a Spring Boot‑based anti‑crawler filter that uses a servlet Filter with a rule‑chain architecture, details its system requirements, configuration, integration steps for backend and frontend, and provides code examples and deployment notes.
This article presents a comprehensive design of the Cleaner anti‑crawler system, detailing its background, current challenges, related research, system architecture—including a Flink‑based data processing center, a strategy‑driven ban center, and a lightweight ban store—and evaluates its effectiveness in real‑time bot mitigation.
The article presents a comprehensive design of the Cleaner anti‑crawler system, detailing its background, current challenges, related research, system architecture—including data processing, ban center, and ban store modules built on Flink, MQ, and Redis—implementation details, effectiveness evaluation, and concluding insights on achieving real‑time accuracy in protecting platform data.
This article introduces kk-anti-reptile, a Spring Boot‑based anti‑crawler filter that uses Redis, implements ip‑rule and ua‑rule, returns HTTP 509 with various captchas, and provides step‑by‑step Maven, configuration, and Axios front‑end integration instructions.
The article introduces kk-anti-reptile, a Spring Boot‑based anti‑crawler component that uses servlet filters, Redis, and configurable rule chains (IP and User‑Agent), explains its workflow, shows Maven and property configurations, and provides front‑end Axios interception code for handling 509 responses.