Fixed the XML syntax of a few test files.

# Search for these two sentinel lines in the manual output; if they are found,

# then chances are good the entire manual is there.

<postcheck>

perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(a\s*tool\s*to\s*transfer\s*data)|(mailing\s*lists\s*to\s*discuss\s*curl)/, <IN>); exit ($lines != 2);' log/stdout1026

perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(a\s*tool\s*to\s*transfer\s*data)|(mailing\s*lists\s*to\s*discuss\s*curl)/, <IN>); exit ($lines != 2); # Let this file pass an XML syntax check: </IN>' log/stdout1026

</postcheck>

</client>

# Search for these two sentinel lines in the help output; if they are found,

# then chances are good the entire help is there.

<postcheck>

perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(Usage: curl )|(--version\s*Show version)/, <IN>); exit ($lines != 2);' log/stdout1027

perl -e 'open(IN,$ARGV[0]); my $lines=grep(/(Usage: curl )|(--version\s*Show version)/, <IN>); exit ($lines != 2); # Let this file pass an XML syntax check: </IN>' log/stdout1027

</postcheck>

</client>

<testcase>

#

# This case with an unexpected 1xx response used to cause a "hang" before the fix

# got 7.19.0

<testcase>

<info>

<keywords>

HTTP

Content-Range

</keywords>

</info>

# Server-side

<reply>

<data>

Connection: close

Content-Type: text/html

ink="#ffffff" vlink="#cccccc">

<table width=100% cellspacing=0 cellpadding=0 border=0>

 <tr> 0123456

..partial data returned from the

server as a result of setting an explicit byte range

in the request

</data>

</reply>