mirror of
https://github.com/moparisthebest/curl
synced 2024-11-04 16:45:06 -05:00
33bea767eb
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.
68 lines
974 B
Plaintext
68 lines
974 B
Plaintext
<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 --trace-ascii log/traceit
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# Verify pseudo protocol after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
opcode: 1
|
|
filename: /284
|
|
mode: octet
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|