curl/tests/data/test716

<testcase>
<info>
<keywords>
HTTP
SOCKS5
all_proxy
</keywords>
</info>
#
# Server-side
<reply>
# method 2 is SOCKS5 asking for user+password
<servercmd>
method 2
</servercmd>
</reply>

#
# Client-side
<client>
<server>
socks5
</server>
<features>
http
proxy
</features>
<name>
SOCKS5 proxy with too long user name
</name>

# it should never connect to the target server
 <command>
http://hohoho.example.com:99/%TESTNUMBER -x socks5://AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA:b@%HOSTIP:%SOCKSPORT
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
97
</errorcode>
</verify>
</testcase>
test: make tests and test scripts use socksd for SOCKS Make all SOCKS tests use socksd instead of ssh. 2019-04-08 13:43:48 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTP`
			`SOCKS5`
			`all_proxy`
			`</keywords>`
			`</info>`
			`#`
			`# Server-side`
			`<reply>`
			`# method 2 is SOCKS5 asking for user+password`
			`<servercmd>`
			`method 2`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`socks5`
			`</server>`
			`<features>`
			`http`
tests: use proxy feature This makes the tests succeed when using --disable-proxy. Closes https://github.com/curl/curl/pull/4488 2019-10-14 16:29:19 -04:00			`proxy`
test: make tests and test scripts use socksd for SOCKS Make all SOCKS tests use socksd instead of ssh. 2019-04-08 13:43:48 -04:00			`</features>`
			`<name>`
			`SOCKS5 proxy with too long user name`
			`</name>`

			`# it should never connect to the target server`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`http://hohoho.example.com:99/%TESTNUMBER -x socks5://AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA:b@%HOSTIP:%SOCKSPORT`
test: make tests and test scripts use socksd for SOCKS Make all SOCKS tests use socksd instead of ssh. 2019-04-08 13:43:48 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
CURLE_PROXY: new error code Failures clearly returned from a (SOCKS) proxy now causes this return code. Previously the situation was not very clear as what would be returned and when. In addition: when this error code is returned, an application can use CURLINFO_PROXY_ERROR to query libcurl for the detailed error, which then returns a value from the new 'CURLproxycode' enum. Closes #5770 2020-08-24 02:39:29 -04:00			`97`
test: make tests and test scripts use socksd for SOCKS Make all SOCKS tests use socksd instead of ssh. 2019-04-08 13:43:48 -04:00			`</errorcode>`
			`</verify>`
			`</testcase>`