Running mitmproxy's reverse-proxy mode locally

[fsturmat]

Problem Description

I have been trying to run mitmproxy's reverse proxy on the same machine that runs the application that is to be "mitm'd". Unfortunately, the good, old hosts-file approach fails because mitmproxy is also using the hosts file to resolve its domain names. I lost my sanity trying to solve this issue.

"How mitmproxy Sucks at Being a Proxy"

Proposal

Maybe some way to let mitmproxy ignore the hosts file... or maybe some way to specify which DNS config mitmproxy should use... or at least some way to have a script perform its own name resolution?

[mhils]

Meta comment: "How mitmproxy Sucks" may not be the best way to provide constructive feedback and introduce yourself. Your actual criticism is well-founded, and that takes away from that point.

On your points:

1. Having a dns_server option would be really nice. We currently just rely on getaddrinfo, which always takes /etc/hosts into account. I've filed Add dns_server option. #6739. Contributions welcome!
2. Re DNS spoofing: Our docs are a bit outdated here, see Nuke dns_spoofing.py addon and fix docs #6738

Last but not least, let me say that #6531 will be the best solution to your original problem, but it's Windows and macOS only for now.

[mhils]

Closing this in favor of the two issues mentioned above - thanks again for filing this!