avwo/whistle
Whistle
Whistle is an HTTP debugging proxy that captures, inspects, and modifies traffic through a web-based management interface. It operates as a man-in-the-middle proxy, intercepting HTTP, HTTPS, HTTP/2, WebSocket, and TCP traffic between clients and servers, and provides a plugin-based architecture that extends core functionality with custom rules, UI panels, and protocol handlers at runtime.
The project distinguishes itself through a combination of capabilities that go beyond basic traffic inspection. It supports server-side headless operation on Linux, allowing it to intercept traffic for applications that cannot directly configure a proxy. Whistle also includes remote page inspection by injecting a Weinre debugging client into web pages, enabling DOM inspection, console logging, and network monitoring from a separate interface. Additionally, it provides request capture and replay with the ability to modify parameters and responses on the fly, and applies user-defined rules to dynamically alter request headers, bodies, URLs, or response data before forwarding.
The tool bridges WebSocket and HTTP/2 connections by forwarding frames and streams while preserving protocol semantics for inspection. Its plugin system enables users to add custom rules and UI features to tailor the debugging environment for specific needs.
Features
- HTTP Proxies - An HTTP, HTTPS, HTTP/2, and WebSocket debugging proxy that captures, inspects, and modifies traffic through a web-based management interface.
- Traffic Proxying and Interception - Intercepts HTTP, HTTPS, HTTP/2, WebSocket, and TCP traffic as a man-in-the-middle proxy for debugging.
- Plugin-Based Debugging Extensions - Adding custom rules and UI features through a plugin system to tailor the debugging environment.
- Plugin Systems - Adds custom rules and UI features through a plugin system to tailor the debugging environment.
- Captured Request Replayers - Captures and replays HTTP requests with editable parameters to test different server responses.
- HTTP Traffic Inspection - Captures and inspects HTTP, HTTPS, HTTP/2, WebSocket, and TCP traffic for debugging and analysis.
- Proxy Servers - Acts as an HTTP proxy on headless Linux servers to intercept traffic for applications unable to set a proxy directly.
- Rule-Driven Modifications - Applies user-defined rules to dynamically alter request headers, bodies, URLs, or response data before forwarding.
- HTTP Request and Response Modifiers - Provides on-the-fly modification of HTTP request headers, bodies, URLs, and responses through user-defined rules.
- Extensible Plugin Architectures - Provides a plugin system that extends core proxy functionality with custom rules, UI panels, and protocol handlers.
- Proxy Plugins - Supports custom plugins to add rules and UI features for tailored traffic inspection and modification.
- Request and Response Transformers - Alters request or response data on the fly by applying configurable rules through a management interface.
- Weinre Debugging Injections - Injects a Weinre remote debugging client into web pages for DOM inspection, console logging, and network monitoring.
- Weinre Page Inspectors - Injects Weinre into web pages for remote debugging of DOM, console logs, and network activity.
- Headless Proxy Servers - Runs as a headless proxy on Linux servers to intercept traffic for applications that cannot configure a proxy directly.
- WebSocket and HTTP/2 Passthrough Proxies - Bridges WebSocket and HTTP/2 connections by forwarding frames and streams while preserving protocol semantics for inspection.
- Weinre Page Inspections - Injects a Weinre remote debugging client into web pages to inspect DOM, console logs, and network activity.
- Weinre Remote Page Inspections - Injects a Weinre debugging client into web pages to inspect DOM, console logs, and network activity.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
