What problem does it solve? When a web application returns 401 Unauthorized or 403 Forbidden on admin panels, API endpoints, or restricted paths, testers need a systematic way to determine whether the access control can be circumvented due to proxy/backend normalization mismatches. ## Core Features & Use Cases - Path Manipulation Matrix: Covers trailing slashes, case changes, URL/double-URL encoding, Unicode overlong encoding, dot segments, null bytes, and path parameters for servers like Tomcat, IIS, Nginx, and Apache. - Method, Header, and Protocol Bypasses: Documents HTTP verb tampering, X-Original-URL/X-Rewrite-URL rewrites, X-Forwarded-For IP spoofing, and HTTP/1.0 downgrade tricks, plus combination attacks. - Decision Tree and Tooling: Provides a prioritized testing workflow and automated scanner guidance (byp4xx, 403bypasser, dirsearch, feroxbuster). - Use Case: During an authorized web penetration test or CTF, a /admin endpoint returns 403; the tester follows the decision tree and discovers /admin..;/ returns 200 on a Tomcat backend, confirming an access control flaw. ## Quick Start Ask the agent to test the forbidden endpoint on the target using the 401/403 bypass playbook, starting with path manipulation tricks and then header-based bypasses.