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
{{ message }}
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.
The MITM Proxy receives a resolved IP address of the target to connect to. This works for most providers but some providers seem to result in undesired behaviour such as wrong upstream proxy selection when going via the target IP address on connect instead of the actual DNS.
Currently one can hack around this — if your provider allows dynamic parts in the proxy url — by including socks5h somewhere in the url, as the MITM proxy Typescript code checks on this. It's however far from ideal.
Better would be to either make this opt-out or opt-in. So that at least we can disable it for the proxy providers that we know it causes issues for.
The text was updated successfully, but these errors were encountered:
More info regarding the proxy provider. Apparently they do not allow by default to target IP addresses (for reasons), and as such this is why we get issues when using target addresses instead of DNS addresses.
The MITM Proxy receives a resolved IP address of the target to connect to. This works for most providers but some providers seem to result in undesired behaviour such as wrong upstream proxy selection when going via the target IP address on connect instead of the actual DNS.
Currently one can hack around this — if your provider allows dynamic parts in the proxy url — by including
socks5h
somewhere in the url, as the MITM proxy Typescript code checks on this. It's however far from ideal.Better would be to either make this opt-out or opt-in. So that at least we can disable it for the proxy providers that we know it causes issues for.
The text was updated successfully, but these errors were encountered: