HDR
Header Modify
Add or override custom HTTP headers by URL match for authentication, debug flags, and environment simulation.
Core features
Put everyday debugging actions in one clear toolbox
DevProxy focuses on high-frequency workflows such as environment switching, production issue reproduction, request rewriting, and script replacement. Save a rule, refresh the page, and it takes effect.
URL
Route Replace
Proxy API or asset requests with matching prefixes to target URLs, ideal for pointing production APIs to local services.
JS
Script Replace
Intercept specific JavaScript files and replace them with custom content for quick validation, reproduction, and fixes.
302
JS Redirect
Redirect selected JS file requests to another URL so production pages can load local or test versions.
PX
Proxy Server
Switch between system proxy, direct connection, and custom proxy servers. Pairs well with whistle for network debugging.
How it works
Designed for real development flows, not buried configuration panels
Click the extension icon in the browser toolbar for common actions, or open the configuration center to maintain full rules and scenarios in one place.
- Enable or disable individual rules for quick switching between tasks.
- Use scenarios to keep separate production, staging, and local debugging combinations.
- Proxy configuration applies immediately, reducing manual system changes and repeated refreshes.
- English and Chinese UI with automatic defaults based on browser language.
Use cases
Built for these development debugging scenarios
Reproduce production issues locally
Redirect JS requests from a production page to a local dev server while keeping the real page context.
Debug APIs across environments
Replace production or staging API prefixes with local services to reduce backend environment switching.
Simulate request headers
Quickly add tokens, debug switches, language markers, or experiment flags to verify server behavior.
Capture traffic with whistle
Point Chrome proxy settings to a local whistle port for request inspection, rewriting, and replay.
Quick start
Start debugging in four steps
Click the DevProxy icon in the Chrome toolbar to open the popup or configuration center.
Select the feature you need: Header, Route, Script, Redirect, or Proxy.
Set the match URL, target URL, header value, script content, or proxy server port.
Save and enable the rule, then refresh the target page to confirm requests and scripts behave as expected.
Permissions
Transparent permission usage
DevProxy requests permissions only to perform development debugging actions that users explicitly configure. The notes below are suitable for Chrome Web Store review and user understanding.
Privacy
Privacy and data handling
DevProxy is a local tool for development debugging. It does not include analytics SDKs and does not upload browsing history, request content, or configuration to external servers.
Stored locally
Rules and preferences are saved in Chrome local storage and used only for extension features.
User configured
Header, route, script, redirect, and proxy rules are created, enabled, and deleted by users.
No default tracking
The extension has no default telemetry, ad tracking, or third-party data sale behavior.
FAQ
FAQ
What should I check if a rule does not work?
Confirm the rule is enabled, the URL prefix matches correctly, and the target page has been refreshed. Script replacement rules should be enabled before the page loads.
Can I enable multiple features at the same time?
Yes. Header, Route, Script, Redirect, and Proxy features are independent and can be combined into different debugging scenarios.
Which proxy tool is recommended?
whistle is recommended. After starting whistle, enter the local address and port in DevProxy's proxy server settings.
Should DevProxy stay enabled for everyday browsing?
It is mainly intended for development debugging. Pause scenarios or disable rules when you are not debugging to avoid affecting normal browsing.
A lighter entry point for Chrome development debugging
DevProxy turns common proxy, redirect, and request rewriting capabilities into simple, controllable rules that help frontend developers locate issues, switch environments, and validate fixes faster.