News for hackers. Stuff that matters.
Re:Making your own web debugging proxy by ejcx on Saturday July 23, 2016 @10:59PM (#12152020)
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 by andersonmvd on Saturday July 23, 2016 @11:02PM (#12152036)
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 by ejcx on Saturday July 23, 2016 @11:09PM (#12152055)
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 by seanp2k2 on Sunday July 24, 2016 @04:51AM (#12152759)
Open testy is awesome for lots of things. However, if I'm doing HTTP debugging, I use curl, Charles, ZAP ( https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Proje... ), tcpdump, and wireshark, in order from simplest to most complex problems.