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//%TESTNUMBER
</command>
</client>

#
# Verify pseudo protocol after the test has been "shot"
<verify>
<protocol>
opcode = 1
mode = octet
tsize = 0
blksize = 512
timeout = 6
filename = /%TESTNUMBER
</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: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`tftp://%HOSTIP:%TFTPPORT//%TESTNUMBER`
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>`
tests: adjust the tftpd output to work with hyper mode By making them look less like http headers, the hyper mode "tweak" doesn't interfere. Enable test 2002 and 2003 in hyper builds (and 1280 which is unrelated but should be enabled). Closes #7658 2021-09-01 21:51:06 +08:00			`opcode = 1`
			`mode = octet`
			`tsize = 0`
			`blksize = 512`
			`timeout = 6`
			`filename = /%TESTNUMBER`
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>`