Live data from Hacker News

Making your own web debugging proxy

twiinsen.com

1–10 of 24 posts

Re: Making your own web debugging proxy

#3

You can do that using MiTM Proxy as well, as explained here: https://dadario.com.br/mitming-ssl-tls-connections/

My problem with using mitm proxy is that it isn't as easy to hack on.

I'm an nginx person, so learning a new python code base to hack on features I want is way harder than having something simple I can add on to, as needed.

Re: Making your own web debugging proxy

#4
post #3

You can do that using MiTM Proxy as well, as explained here: https://dadario.com.br/mitming-ssl-tls-connections/

My problem with using mitm proxy is that it isn't as easy to hack on. I'm an nginx person, so learning a new python code base to hack on features I want is way harder than having something simple I can add on to, as needed.

I found easy to get started, it's as simple as the post. The real benefit I see is to plug arbitrary python code to hack requests and responses. It's very good, but I've noticed some crashes in my experiments too.

Re: Making your own web debugging proxy

#5
>They all had good features, but none had all of my desired features.

Many intercepting proxies like The Fiddler with FiddlerScript and the Burp Suite through Burp Extender can be extended to have any feature you want by writing your own code or leveraging someone else's. Personally the only time I've found myself thinking I might need nginx for a debugging proxy is when I need scale. I'd rather use something that's close enough, write stuff where I need to, then focus on doing really cool things with them like finding vulnerabilities for fun and profit.

Re: Making your own web debugging proxy

#6
post #3

Earlier quoted context omitted.

My problem with using mitm proxy is that it isn't as easy to hack on. I'm an nginx person, so learning a new python code base to hack on features I want is way harder than having something simple I can add on to, as needed.

I found easy to get started, it's as simple as the post. The real benefit I see is to plug arbitrary python code to hack requests and responses. It's very good, but I've noticed some crashes in my experiments too.

That's what the benefit of using openresty is. I can print and hack on http requests in an already mature ecosystem.

It's two ways to do the same thing, but I like my way, and mine uses software that is production ready as a proxy :)

Re: Making your own web debugging proxy

#8

>They all had good features, but none had all of my desired features. Many intercepting proxies like The Fiddler with FiddlerScript and the Burp Suite through Burp Extender can be extended to have any feature you want by writing your own code or leveraging someone else's. Personally the only time I've found myself thinking I might need nginx for a debugging proxy is when I need scale. I'd rather use something that's…

i've gone through the very basics of burp suite before but never effectively used it to test much.

so, i did a tutorial search for myself, and if anyone may benefit here's a text one with screenshots: https://www.pentestgeek.com/web-applications/burp-suite-tuto...

and some official video tutorials: https://portswigger.net/burp/tutorials/

Re: Making your own web debugging proxy

#9
"The all had good features, but..."

I sympathize with the author. I find that all of the alternatives are unsatisfactory.

I made my own solution that handles HTTPS and, most importantly, gzip compression. It's 22 lines of portable shell script including comments. It uses only two small programs: socat and netsed. The limitation is I only use it to proxy one domain at a time.

I tried to offer it to HN readers via "Ask HN" but for some reason the mods quickly banned the account.

Post reply on HN