AI 产品解读Intercept, modify, and mock HTTP(S) network requests and responses directly in the Chrome browser
Enables web developers and QA engineers to modify network traffic (redirect URLs, modify headers, inject scripts, mock API responses) without setting up a proxy server, avoiding VPN issues and latency. Allows frontend development when backend APIs aren't ready, testing local JS/CSS changes on production sites, and overriding REST/GraphQL API responses.
User installs the extension, creates HTTP rules (redirect, headers, script injection, mock API responses) via the extension popup or the Requestly web app at app.requestly.io. Rules are stored locally in chrome.storage.local. When browsing, the service worker intercepts matching requests using declarativeNetRequest and webRequest APIs, applies the configured rules, and optionally records sessions for replay. The extension integrates with the Requestly web app for advanced rule management, team collaboration, and cloud sync.
URL redirect rulesHTTP header modification (request and response)JavaScript and CSS injection into pagesREST and GraphQL API response mockingAPI request/response body and status code overrideSession recording and replay
- 目标用户
- Web developers / QA engineers / Frontend developers / DevOps engineers / API testers
- Source code is heavily minified making detailed logic analysis difficult
- Could not definitively determine if the web app UI (popup React app) requires login or renders locally without auth
- The devtools/index.js is 1.69MB minified - deep inspection was not feasible within tool budget
付费分析未识别到付费功能
No payment-related code found in the extension source: no premium/subscription/billing/pricing/upgrade/stripe keywords detected. The 'checkout' matches are all from the rrweb session recording library (checkoutEveryNms, isCheckout parameters) which is session replay checkpoint terminology, not payment. The extension is open source (https://github.com/requestly/requestly/). No feature gating, license checks, or payment UI found in the extension code. The destination service (Requestly/BrowserStack) likely has paid team/enterprise plans, but the extension itself does not gate features behind payment.
- 置信度
- 70
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 是
- 登录理由
- The extension's core rule-application engine works locally without login (rules stored in chrome.storage.local). However, the extension heavily integrates with the Requestly web app at app.requestly.io for session recordings (SESSIONS_URL), rule management UI, team collaboration, and cloud sync. The app.cs.js content script injects on requestly domains to bridge the extension and web app. Session recording drafts open at app.requestly.io/sessions/draft/{id}, and the externally_connectable manifest connects to BrowserStack domains. Login to the destination service (Requestly web app) is required for the full workflow including cloud features, session replay, and team collaboration.
A superb tool for effortless network control. Instantly redirect, block, or modify requests through a powerful yet clean UI.
This is by far my extension using which I modify headers and add/edit Scripts wherever required. Awesome Extension
This is my best go to extension during Header modification or adding Scripts. Excellent
amazing extension to mock / intercept responses
很不错
Superb tool. It makes it easy to redirect, block, or modify network requests without much setup. The UI is clean, and the features are powerful.
Great app to mock most of the http request, from intercepting to json testing
Using more than a year, and a game changer for testing various things, test local changes without actually running the full frontend on local.
As an Automation QA engineer, I’ve found Requestly to be a practical and flexible tool for modifying HTTP traffic directly in the browser. It fills a gap where dev tools and network proxies fall short, especially when you need to quickly mock API responses, bypass certain request conditions, or test edge cases on the fly. The ability to intercept and alter JSON response bodies without spinning up a local mock server is a major time-saver during exploratory testing or verifying frontend behavior against non-ideal backend scenarios. That said, the UI takes a bit of getting used to, and complex rules can become hard to manage if you work across multiple projects. I’d appreciate more structured rule grouping or export/import presets by workspace.
Very useful tools for Web Devs. Helps a lot !