curl/tests/data/test283

<testcase>
<info>
<keywords>
TFTP
TFTP RRQ
FAILURE
</keywords>
</info>

#
# Client-side
<client>
<server>
tftp
</server>
 <name>
TFTP retrieve on invalid file
 </name>
 <command>
tftp://%HOSTIP:%TFTPPORT//invalid-file --trace-ascii log/traceit --tftp-blksize 1024
</command>
</client>

#
# Verify pseudo protocol after the test has been "shot"
<verify>
<errorcode>
69
</errorcode>
<protocol>
opcode: 1
mode: octet
tsize: 0
blksize: 1024
timeout: 6
filename: /invalid-file
</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`<testcase>`
Added test of TFTP server error reporting. 2007-01-09 22:32:19 -05:00			`<info>`
			`<keywords>`
			`TFTP`
			`TFTP RRQ`
Don't tear down the ftp connection if the maximum filesize was exceeded and added tests 290 and 291 to check. 2007-03-29 21:13:47 -04:00			`FAILURE`
Added test of TFTP server error reporting. 2007-01-09 22:32:19 -05:00			`</keywords>`
			`</info>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`tftp`
			`</server>`
			`<name>`
			`TFTP retrieve on invalid file`
			`</name>`
			`<command>`
tftp tests: verify sent options too The tftpd test server now logs all received options and thus all TFTP test cases need to match them exactly. Extended test 283 to use and verify --tftp-blksize. 2015-11-06 04:52:19 -05:00			`tftp://%HOSTIP:%TFTPPORT//invalid-file --trace-ascii log/traceit --tftp-blksize 1024`
Added test of TFTP server error reporting. 2007-01-09 22:32:19 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify pseudo protocol after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`69`
			`</errorcode>`
			`<protocol>`
			`opcode: 1`
			`mode: octet`
tftp tests: verify sent options too The tftpd test server now logs all received options and thus all TFTP test cases need to match them exactly. Extended test 283 to use and verify --tftp-blksize. 2015-11-06 04:52:19 -05:00			`tsize: 0`
			`blksize: 1024`
			`timeout: 6`
			`filename: /invalid-file`
Added test of TFTP server error reporting. 2007-01-09 22:32:19 -05:00			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`</testcase>`