Home
last modified time | relevance | path

Searched refs:socks4 (Results 1 – 15 of 15) sorted by relevance

/external/curl/tests/data/
Dtest70215 # 91 is socks4 failure
24 socks4
34 --socks4 %HOSTIP:%SOCKSPORT http://%HOSTIP:%NOLISTENPORT
Dtest70034 socks4
40 --socks4 %HOSTIP:%SOCKSPORT http://%HOSTIP:%HTTPPORT/700
Dtest70834 socks4
37 all_proxy=socks4://%HOSTIP:%SOCKSPORT
Dtest70636 socks4
42 --socks4 %HOSTIP:%SOCKSPORT ftp://%HOSTIP:%FTPPORT/
Dtest70426 --socks4 %HOSTIP:%NOLISTENPORT http://%HOSTIP:%HTTPPORT/704
Dtest56430 socks4
/external/curl/docs/cmdline-opts/
Dsocks4.d1 Long: socks4
13 Since 7.21.7, this option is superfluous since you can specify a socks4 proxy
14 with --proxy using a socks4:// protocol prefix.
Dpreproxy.d12 alternative proxy protocols. Use socks4://, socks4a://, socks5:// or
Dsocks5.d22 This option (as well as --socks4) does not work with IPV6, FTPS or LDAP.
DMakefile.inc195 socks4.d socks5.d \
Dpage-footer72 .IP "socks4://"
73 Makes it the equivalent of --socks4
/external/curl/docs/
Doptions-in-versions197 --socks4 7.15.2
/external/curl/tests/server/
Dsocksd.c300 static curl_socket_t socks4(curl_socket_t fd, in socks4() function
375 return socks4(fd, buffer, rc); in sockit()
/external/curl/tests/
DFILEFORMAT.md319 - `socks4`
/external/curl/
DCHANGES6881 - socks4: fix host resolve regression
6883 1. The socks4 state machine was broken in the host resolving phase