SOCKS Proxy in Proxyman routes traffic to the Host header instead of the specified SOCKS destination

Description

When using a SOCKS5 proxy with Proxyman, the traffic is incorrectly routed based on the Host header rather than the destination specified by the SOCKS proxy. This leads to incorrect proxy behavior, where traffic is not directed to the intended target but instead to whatever is specified in the Host header. This behavior undermines the purpose of using a SOCKS proxy and could result in incorrect routing and potential security issues.

Steps to Reproduce:

1. Configure Proxyman to use a SOCKS5 proxy.
2. Initiate traffic that should be routed through the SOCKS proxy.
3. Observe that traffic is routed to the address in the Host header instead of the SOCKS destination.
4. Expected Behavior:
5. Traffic should be routed through the SOCKS proxy to the correct destination as specified, not the Host header.

Environment

• App version: v5.7.0
• macOS version: macOS Sonoma 14.5