Searched refs:socks4 (Results 1 – 15 of 15) sorted by relevance
15 # 91 is socks4 failure24 socks434 --socks4 %HOSTIP:%SOCKSPORT http://%HOSTIP:%NOLISTENPORT
34 socks440 --socks4 %HOSTIP:%SOCKSPORT http://%HOSTIP:%HTTPPORT/700
34 socks437 all_proxy=socks4://%HOSTIP:%SOCKSPORT
36 socks442 --socks4 %HOSTIP:%SOCKSPORT ftp://%HOSTIP:%FTPPORT/
26 --socks4 %HOSTIP:%NOLISTENPORT http://%HOSTIP:%HTTPPORT/704
30 socks4
1 Long: socks413 Since 7.21.7, this option is superfluous since you can specify a socks4 proxy14 with --proxy using a socks4:// protocol prefix.
12 alternative proxy protocols. Use socks4://, socks4a://, socks5:// or
22 This option (as well as --socks4) does not work with IPV6, FTPS or LDAP.
195 socks4.d socks5.d \
72 .IP "socks4://"73 Makes it the equivalent of --socks4
197 --socks4 7.15.2
300 static curl_socket_t socks4(curl_socket_t fd, in socks4() function375 return socks4(fd, buffer, rc); in sockit()
319 - `socks4`
6881 - socks4: fix host resolve regression6883 1. The socks4 state machine was broken in the host resolving phase