curl/tests/data/test1530

<testcase>
<info>
<keywords>
CURLOPT_OPENSOCKETFUNCTION
</keywords>
</info>

<client>
<server>
none
</server>
<features>
http
</features>
<tool>
lib1530
</tool>
 <name>
CURLOPT_OPENSOCKETFUNCTION returns bad socket
 </name>
</client>

# it should be detected and an error should be reported
<verify>
# 7 == CURLE_COULDNT_CONNECT
<errorcode>
7
</errorcode>
</verify>
</testcase>
CURLOPT_OPENSOCKETFUNCTION: return error at once When CURL_SOCKET_BAD is returned in the callback, it should be treated as an error (CURLE_COULDNT_CONNECT) if no other socket is subsequently created when trying to connect to a server. Bug: http://curl.haxx.se/mail/lib-2015-06/0047.html 2015-06-09 00:22:02 +02:00			`<testcase>`
			`<info>`
			`<keywords>`
			`CURLOPT_OPENSOCKETFUNCTION`
			`</keywords>`
			`</info>`

			`<client>`
			`<server>`
			`none`
			`</server>`
test1530: added http to required features 2015-06-14 22:38:39 +02:00			`<features>`
			`http`
			`</features>`
CURLOPT_OPENSOCKETFUNCTION: return error at once When CURL_SOCKET_BAD is returned in the callback, it should be treated as an error (CURLE_COULDNT_CONNECT) if no other socket is subsequently created when trying to connect to a server. Bug: http://curl.haxx.se/mail/lib-2015-06/0047.html 2015-06-09 00:22:02 +02:00			`<tool>`
			`lib1530`
			`</tool>`
			`<name>`
			`CURLOPT_OPENSOCKETFUNCTION returns bad socket`
			`</name>`
			`</client>`

			`# it should be detected and an error should be reported`
			`<verify>`
			`# 7 == CURLE_COULDNT_CONNECT`
			`<errorcode>`
			`7`
			`</errorcode>`
			`</verify>`
			`</testcase>`