Replies: 1 comment
-
I had something similar to this when doing testing with ignore_hosts. See if this thread has any applicability in your case: #5638 @mhils suggested to vary the https version that curl was using and that provided insight into what was going on. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to run a mitmproxy instance that modifies specific requests and ignores all other requests. I'm running mitmproxy via the official docker container, and I'm providing it 2 trusted certificates, one for the hostname of the proxy and one for the hostname I care about.
Here's how I'm invoking it for my test:
With that running, I see the following:
http://frameproxy.a-rwx.org:8080
,curl -v icanhazip.com
andcurl -v frame.akerl.app
both work.https://frameproxy.a-rwx.org:8080
,curl -v icanhazip.com
andcurl -v frame.akerl.app
both work.If I modify the options to set allow_hosts to frame.akerl.app:443,
HTTPS_PROXY=http://frameproxy.a-rwx.org:8080
(non-HTTPS proxy) still works, but suddenly any requests withHTTPS_PROXY=https://frameproxy.a-rwx.org:8080
just hang like this:I never see any indication in the mitmproxy interface of the connection. the CONNECT is sending the matching hostname.
I get the exact same behavior if instead of allow_hosts, I set ignore_hosts to icanhazip.com:443: in both cases, setting the filter causes all requests to the proxy via HTTPS to stall.
What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions