What problem does it solve? When an API gateway returns 403 for protected routes, testers need a systematic way to check whether the gateway and backend normalize paths differently, because that mismatch can expose admin APIs to unauthorized access. ## Core Features & Use Cases - Path Normalization Payloads: Provides dot-segment, double-slash, URL-encoding, semicolon, and backslash variants that exploit gateway/backend parsing differences. - Method Override & Version Fallback: Covers X-HTTP-Method-Override headers and legacy API version paths (v1, unversioned) that gateways forget to protect. - Gateway-Specific Techniques: Documents Kong, Nginx, and AWS API Gateway specific bypasses, plus rate-limit evasion and API documentation discovery (swagger.json, /v3/api-docs). - Use Case: During an authorized SRC test, a target returns a Kong-flavored 403 on /api/admin; apply the normalization payload list to find /api/%2e/admin reaches the backend, then confirm with a rejected-vs-bypassed request pair as evidence. ## Quick Start Ask the agent to test the target's 403 API gateway endpoints for path normalization and method override bypasses using this manual.