From 95c4db824e5d759e547170f493028a79e5bcbf9e Mon Sep 17 00:00:00 2001 From: John Costa Date: Tue, 20 Jan 2026 19:20:29 +0000 Subject: [PATCH] gist about mitmproxy --- content/gists/mitmproxy.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 content/gists/mitmproxy.md diff --git a/content/gists/mitmproxy.md b/content/gists/mitmproxy.md new file mode 100644 index 0000000..f5c8c26 --- /dev/null +++ b/content/gists/mitmproxy.md @@ -0,0 +1,26 @@ ++++ +title = "Mitmproxy - My new best friend" +date = "2026-01-20" +author = "John Costa" +tags = ["Software", "tools", "gist"] ++++ + +[mitmproxy](https://www.mitmproxy.org) is - as the name suggests - a proxy. + +At [Requesty](https://requesty.ai), I do a lot of request manipulation, from one format to another. We listen to a lot of streams. Basically we do a lot of networking. + +So, when I need to understand the shape of my outgoing requests, where logging or debugging might be enough, I reach for `mitmproxy`. + +You start it by: + +``` +mitmproxy --mode reverse:https://google.com +``` + +I use it in `reverse` mode almost exclusively. This is because I mostly want to debug outbound requests. + +Then all you have to do is make a request! + +`mitmproxy` will show you all your outbound requests, the response, the headers and a lot more options (you can even replay requests!). + +If you do any kind of requests and have ever had to debug them, I highly recommend you give this tool a try.