One-click debugging for HTTP(S) ↦
HTTP View is a desktop tool for supercharged HTTP(S) debugging. It gives you one-click setup for HTTP and HTTPS interception, and all the tools you need to quickly explore, examine and understand the HTTP your code (or anybody else’s) is sending.
Open source, cross-platform, and easy on the eyes. This is definitely worth a look.
Sign in or Join to comment or subscribe
Hi Changelog readers! I’ve only just launched this first release last week, so it’s all very new and exciting.
This first version is totally free and open-source - give it a go, and I’d love to hear what you think so far, and where you think I should take it next.
Jerod co-hosts The Changelog, crashes JS Party, and takes out the trash (his old code) once in awhile.
Cool stuff for sure, Tim! 👏
Are you the only one working on this project? It appears you’re trying to build a business around it. Maybe you could share why you decided to build this and what some of your long-term goals are for the endeavor…
Yes it’s just me, plus a good sprinkling of open-source contributions from others.
I started building HTTP Toolkit because I tried to use Fiddler on my Linux laptop one time, and after a bunch of awkward Mono setup to get it installed, it immediately crashed and broke some obscure Gnome proxy settings en route, totally cutting off my internet, and leaving me to debug the whole thing via my phone. It was a dark time.
In general there’s a few tools in this space, but none of them integrate nearly as well as they could with modern development tools, none of them are open-source or very actively maintained, and they all feel like rough proof of concepts, rather than serious developer tools we can use daily and rely on.
The long-term plan from here is indeed to turn this into business to make it sustainable, and build it into the suite of solid powerful HTTP developer tools we’re missing. The core features here are all staying free, and there’ll be a paid Pro version coming sometime soon to add more advanced features on top. Exactly where to draw that line is TBC, but I’m currently planning paid features like automated security analysis of CSP headers & HTTPS configuration, integrations with other tools, HAR/code snippet exports, request/response diffing, and so on. I’d definitely welcome ideas there too!