46 lines
742 B
Plaintext
46 lines
742 B
Plaintext
|
<testcase>
|
||
|
|
<info>
|
||
|
|
<keywords>
|
||
|
|
SFTP
|
||
|
|
multi
|
||
|
|
</keywords>
|
||
|
|
</info>
|
||
|
|
|
||
|
|
# Server-side
|
||
|
|
<reply>
|
||
|
|
<data>
|
||
|
|
</data>
|
||
|
|
</reply>
|
||
|
|
|
||
|
|
# Client-side
|
||
|
|
<client>
|
||
|
|
<server>
|
||
|
|
sftp
|
||
|
|
</server>
|
||
|
|
<tool>
|
||
|
|
lib583
|
||
|
|
</tool>
|
||
|
|
<name>
|
||
|
|
SFTP with multi interface, remove handle early
|
||
|
|
</name>
|
||
|
|
|
||
|
|
# The command here uses 'localhost' just to make sure that curl_multi_perform
|
||
|
|
# won't reach too far in the first invoke. When using c-ares at least, the
|
||
|
|
# name resolve will cause it to return rather quickly and thus we could trigger
|
||
|
|
# the problem we're looking to verify.
|
||
|
|
<command>
|
||
|
|
sftp://localhost:%SSHPORT%POSIX_PWD/log/upload583.txt %USER:
|
||
|
|
</command>
|
||
|
|
</client>
|
||
|
|
|
||
|
|
# Verify data after the test has been "shot"
|
||
|
|
<verify>
|
||
|
|
<valgrind>
|
||
|
|
disable
|
||
|
|
</valgrind>
|
||
|
|
<errorcode>
|
||
|
|
0
|
||
|
|
</errorcode>
|
||
|
|
</verify>
|
||
|
|
</testcase>
|