Master Whistle: Fast Proxy Setup for Frontend Debugging

1. Introduction

After trying several network‑request proxy tools, the author chose Whistle (developed by avenwu@tencent) for its high efficiency and ease of use, solving long‑standing debugging problems.

Compared with Fiddler and Charles, Whistle offers a more streamlined experience, especially when combined with the Chrome extension proxyOmega for one‑click proxy switching.

2. Steps

1. Host mapping and sub‑path host mapping

2. Local file or path replacement

3. Request forwarding

4. Script injection (HTML/JS/CSS)

5. Matching patterns (regex)

6. Ignoring specific request content

7. Request rewriting and API mock

Values such as

test_ua

and

mock-price

can be set to return mock data directly, which is very convenient.

8. Remote debugging

Proxy a mobile device’s requests to Whistle by using the machine’s IP and the default port 8899.

9. HTTPS proxy setup

HTTPS configuration is documented at https://avwo.github.io/whistle/webui/https.html .

3. Summary

The listed features cover the most common Whistle usage scenarios for frontend development; additional advanced capabilities are available in the official documentation.