Comment by synergy20
2 years ago
how is this different from devtools? is the main selling point easy of use, or more extra features on top of devtools?
2 years ago
how is this different from devtools? is the main selling point easy of use, or more extra features on top of devtools?
Yes: ease of use, lots of additional power (for starters, you can modify traffic, not just view it) and being able to intercept anything (multiple tabs, multiple browsers, mobile, docker, CLI tools, backend services, you name) all in the same interface.
For the web dev case, for example, if you're debugging some interaction that means you can intercept your browser <-> server traffic and your server <-> upstream API traffic all in the same place, and see the full flow, and you can modify server responses or backend API responses in flight, to test out different edge cases.
There's a Chrome dev tools vs HTTP Toolkit comparison page here with a little more detail: https://httptoolkit.com/chrome-devtools-alternative/
That's very cool - does it support corporate proxy stuff like PAC files, HTTPS, NTLM, Kerberos, authenticating with current user, etc? For example would I be able to write a rule to capture traffic going to certain proxies and redirect it to another proxy? Sorry if this is explained somewhere already but I couldn't find anything about it on your webpage or github. Many thanks for your time!