You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered:
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:
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!
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?
The text was updated successfully, but these errors were encountered: