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.
Invaluable tool for web development in our environment. I can't speak to pricing or plans, but we get great support.
Requestly is an incredibly useful tool for developers, whether you're working on a large team with multiple staging environments, numerous application endpoints for various APIs, databases, services, front-ends, or even working solo or just on a local environment. While it has advanced features making it useful for just about any development scenario one can think of, it's also easy enough to use for anyone that is new to web development or just looking to poke around and learn more about how networking happens under-the-hood. Requestly does all the work of setting up a proxy server, configuring the browser, managing certificates, and all the bootstrapping required to do simple things like redirect network requests or more advanced operations such as modifying headers or even the network response altogether. Great if you are troubleshooting or testing an application and need to emulate a certain network response. The Sessions feature is especially useful for documenting solutions, issues for Github or sharing with others since it captures the relevant network traffic, grabs a screen recording, and enables others to easily reproduce it all in one shot (which otherwise is a time-consuming effort). Requestly combines all the power of complicated tools like Charles Proxy and many of the features of something like Postman all in one app/chrome extension. I highly recommend giving it a try if you haven't already–it will make your dev work so much easier.
Great extension, but sadly looks like I will not be able to use it anymore due to the pricing. I usually run apps in different ports, thus having different headers for different ports, and I have more than 10 rules. However, for a use case similar to mine with only header modifications, seems like $15 a month is too much to pay, more than a Netflix subscription tbh (just a personal opinion that it's too much; I may be wrong)! I am sure a lot of your user-base use this extension for just headers, and I hope in future you could create a cheaper plan that ONLY enables the headers feature. Falling back to mode headers (which I really don't like) until then.
Same here. It no longer works since the recent update. With this extension, even regular websites which are out of rules don't work properly. With rules, also don't work. They totally failed on their update
awsome
I don't know what they've done after the recent update... it was working fine before that. Now it doesn't even open the website for me to make new rules or remove them. Sometimes the rules don't work. And now, I can't even login, and IDK why it keeps logging me out of my account. What an upgrade... Wow...
After a recent update they limited the number of rules we could apply. No point using it.
So far so good. Using it to redirect ads.doubleclick.net URLs to the merchant URL.
Seems to have stopped working since the update that also included Rule notified widget overlay. The widget says my rules are applied, but it wasn't actually doing it. UPDATE: I found the issue. I tried saving my existing rule and couldn't do it because apparently "negative lookahead" in RegExp is no longer supported. Looks like there was an update that caused that to stop working, but it didn't notify the users about the already saved rules that contain those. As a result, the rule just failed silently.
I used to use this extension almost daily for work and for website development. It has recently started adding overlays and extra scripts to websites which interfere with developer work. I can't use this anymore.