curl/tests/data/test284

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

#
# Server-side
<reply>
<data>
A chunk of data which exactly fits into
a 512 byte TFTP block, testing a boundary
condition in the TFTP receive code.
789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
123456789ABCDEF
</data>
</reply>

#
# Client-side
<client>
<server>
tftp
</server>
 <name>
TFTP retrieve of boundary case 512 byte file
 </name>
 <command>
tftp://%HOSTIP:%TFTPPORT//284
</command>
</client>

#
# Verify pseudo protocol after the test has been "shot"
<verify>
<protocol>
opcode: 1
mode: octet
tsize: 0
blksize: 512
timeout: 6
filename: /284
</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-23 10:25:56 +08:00			`<testcase>`
Added test for TFTP retrieve of boundary case 512 byte file. 2007-01-11 07:40:22 +08:00			`<info>`
			`<keywords>`
			`TFTP`
			`TFTP RRQ`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`A chunk of data which exactly fits into`
			`a 512 byte TFTP block, testing a boundary`
			`condition in the TFTP receive code.`
			`789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`123456789ABCDEF`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`tftp`
			`</server>`
			`<name>`
			`TFTP retrieve of boundary case 512 byte file`
			`</name>`
			`<command>`
tests: removed redundant --trace-ascii arguments This is already added by the test suite; it's not clear why all these tests had it, unless it's cargo-culting. 2017-05-10 01:43:22 +08:00			`tftp://%HOSTIP:%TFTPPORT//284`
Added test for TFTP retrieve of boundary case 512 byte file. 2007-01-11 07:40:22 +08: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 17:52:19 +08:00			`tsize: 0`
			`blksize: 512`
			`timeout: 6`
			`filename: /284`
Added test for TFTP retrieve of boundary case 512 byte file. 2007-01-11 07:40:22 +08: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-23 10:25:56 +08:00			`</testcase>`