Believe it or not, the most common use-case is simply discovering what your code is actually doing. Modern frameworks are often so far removed from the nuts an

Believe it or not, the most common use-case is simply discovering what your code is actually doing. Modern frameworks are often so far removed from the nuts and bolts of HTTP and TCP that it can be difficult to know what's actually happening on the wire without using a tool like this. A similar frustration is the tendency for SDK / library vendors to document their product using code snippets in various languages, but without simply showing you what the raw HTTP requests look like. Typically the closest you can get is a set of curl commands. When you show me a python/ruby/swift/js snippet, I have a guess as to what's happening. When you show me HTTP, I know exactly what's going on. And if you won't show me HTTP, time to fire up mitmproxy.