curl/tests/data/test271

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

#
# Server-side
<reply>
<data>
a chunk of
data
returned
 to client
</data>
</reply>

#
# Client-side
<client>
<server>
tftp
</server>
 <name>
TFTP retrieve
 </name>
 <command>
tftp://%HOSTIP:%TFTPPORT//271 --trace-ascii log/traceit
</command>
</client>

#
# Verify pseudo protocol after the test has been "shot"
<verify>
<protocol>
opcode: 1
mode: octet
tsize: 0
blksize: 512
timeout: 6
filename: /271
</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>`
test 271, the first ever TFTP test 2005-09-19 18:04:06 -04:00			`<info>`
			`<keywords>`
			`TFTP`
			`TFTP RRQ`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`a chunk of`
			`data`
			`returned`
			`to client`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`tftp`
			`</server>`
			`<name>`
			`TFTP retrieve`
			`</name>`
			`<command>`
based on Tor Arntsen's fix, this should correct test case 271 to again run fine 2006-05-24 11:22:03 -04:00			`tftp://%HOSTIP:%TFTPPORT//271 --trace-ascii log/traceit`
test 271, the first ever TFTP test 2005-09-19 18:04:06 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify pseudo protocol after the test has been "shot"`
			`<verify>`
			`<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: 512`
			`timeout: 6`
			`filename: /271`
test 271, the first ever TFTP test 2005-09-19 18:04:06 -04: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>`