Gaurav Jain
Gaurav Jain
> ``` > dns nameserver 8.8.8.8 > ``` This line should be `nameserver 8.8.8.8` and is the root cause behind mitmproxy not being able to get the system dns servers
Proxy debug: https://gist.github.com/errorxyz/0f81b5d8ef3d1921e1b2deb08c24e990
> I can't repro this here - cloudflare-quic.com works just fine both in local and redirect mode. It works just fine for you in reverse mode, only local mode is...
> Isn't this something that every dual stack server is going to see? I don't see this being the case for dual stacked TCP based reverse proxies for eg. http...
> This may be because we're not completing both TCP handshakes here. With UDP we don't have a handshake, so we have a "connection" immediately. Agreed, but for QUIC flows...
> Does modifying `connection_strategy` change anything? Yes, I don't see the IPv4 connection now: ``` mitmdump --mode reverse:http3://http3.is --set connection_strategy=lazy [18:17:18.498] reverse proxy to http3://http3.is listening at *:8080. [18:17:18.983][[::1]:51502] client...
This line here is the culprit: https://github.com/mitmproxy/mitmproxy/blob/74424df83908565d060b7a9058c49ab99be24b4a/mitmproxy/proxy/layers/quic.py#L915 This takes around 250ms on windows and 20ms on linux.
> Is this only for the first request going through the proxy, or for every request? For every request. More specifically, this line is executed a few times before TLS...
Hey! I'm interested in working on this issue. How do you want to go about the implementation? I have a few ideas: - a shell with limited functionality(each command has...
> Hey! I'm interested in working on this issue. How do you want to go about the implementation? I have a few ideas: > > * a shell with limited...