e2c6e00570
I've now made TFTP "connections" not being kept for re-use within libcurl. TFTP is UDP-based so the benefit was really low (if even existing) to begin with so instead of tracking down to fix this problem we instead removed the re-use. I also enabled test case 1099 that I wrote a few days ago to verify that this change fixes the reported problem.
46 lines
625 B
Plaintext
46 lines
625 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
TFTP
|
|
TFTP RRQ
|
|
FAILURE
|
|
</keywords>
|
|
</info>
|
|
|
|
<reply>
|
|
<data nocheck="yes">
|
|
data for 1099
|
|
</data>
|
|
</reply>
|
|
|
|
#
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
tftp
|
|
</server>
|
|
<name>
|
|
TFTP get first a non-existing file then an existing
|
|
</name>
|
|
<command>
|
|
tftp://%HOSTIP:%TFTPPORT/an/invalid-file tftp://%HOSTIP:%TFTPPORT//1099 --trace-ascii log/traceit
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# Verify pseudo protocol after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
opcode: 1
|
|
filename: an/invalid-file
|
|
mode: octet
|
|
opcode: 1
|
|
filename: /1099
|
|
mode: octet
|
|
</protocol>
|
|
<stdout mode="text">
|
|
data for 1099
|
|
</stdout>
|
|
</verify>
|
|
</testcase>
|