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.
perfect tool. I wish it has how much time request execute
Using this tool so much time and happy with it
Great!
Awesome
Great!
asd
Nice functional app
I’ve been using Requestly for a while, and it has completely changed how I debug and test web applications. The ability to redirect URLs, modify headers, or mock API responses on the fly is extremely powerful. Simple UI and powerful features - highly recommended!
Top Produkt! Ich bin Frontend-Entwickler und schaffe an einem Highend Platform mit Microfrontend App. Ich tue lokal entwickeln damit und spare mir somit Stunden an Debugging Zeit, weil ich einfach die Assets ersetzen konnte mit meinem lokalen Instanz. Es gab aber ein kleines Problem: Bei Aktivierung von Requestly mit "Network Logging" (Network Interception) tritt ein SSL-Zertifikatsfehler auf: **Fehlermeldung:** "Problem bei der Netzwerkkonfiguration - Es sieht so aus, als ob 'ROProxyCA' das falsche SSL-Zertifikat [...] sendet" Ich hoffe, dass dies baldst gelöst wird :).
great!