Chrome shows "ERR_PROXY_CONNECTION_FAILED" when using dynamic tunnel

[printff]

Browser: Windows 10, Chrome 105
WindTerm: 2.6.0 pre 1

Open a dynamic proxy tunnel on port 1080, Chome use this socks5 proxy to browse, page shows "ERR_PROXY_CONNECTION_FAILED".
Using xshell to open dynamic tunnel doesnot has this matter.

[vomobile]

The same issue on 2.5.0 (Linux).
Chrome page shows "ERR_SSL_PROTOCOL_ERROR", and Firefox page shows "PR_END_OF_FILE_ERROR".
But the dynamic SSH Tunnel with PuTTY worked.

[tinyhare]

Windows 10 , Chrome + SwitchyOmega , WindTerm 2.6.0 Prerelease
get ERR_SSL_PROTOCOL_ERROR

I find the second response of SOCKS5 is different from SecureCRT, and not sure it's the key problem:

I read the rfc1928, it is not clear what this used for, and some questions on internet said it is used for connect to the SOCKS relay server, if it retruen addr 0.0.0.0 and port 0, it means Use the "SOCKS server as the relay server"

About the relay server , I only find it in rfc1928 at UDP section:
7. Procedure for UDP-based clients

A UDP-based client MUST send its datagrams to the UDP relay server at
the UDP port indicated by BND.PORT in the reply to the UDP ASSOCIATE
request.

[kingToolbox]

Duplicate of #26

WindTerm_2.7.0_Prerelease_3 fixes the bug where dynamic port forwarding couldn't proxy DNS lookups. Please download and try it. Thank you.

@tinyhare
Wow, you're amazing! Your analysis is completely correct. It was precisely the response in that field that was causing the issue. When I initially implemented it, I overlooked the protocol detail that for Domain Name(3) responses, domain name resolution and replying with IPv4(1) or IPv6(2) was required. That's why I mistakenly returned Domain Name(3) with 0.0.0.0.