This leads to a conflicting situation when using a Go program that uses both the standard HTTP client and the chisel client and needs to go through a SOCKS proxy (such as the portainer agent).
Was there any reason to only allow for the socks:// instead of socks5:// in the chisel client?
The current version of chisel only allows the client to use
socks://orsocks5h://as proxy protocol:However, Golang only supports the
socks5://proxy protocol for its HTTP client:This leads to a conflicting situation when using a Go program that uses both the standard HTTP client and the chisel client and needs to go through a SOCKS proxy (such as the portainer agent).
Was there any reason to only allow for the
socks://instead ofsocks5://in the chisel client?