curl/tests/data/test158

<testcase>
# Server-side
<reply>
<data>
HTTP/1.1 100 Continue swsclose
Silly-header: yeeeees

</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP multipart formpost with only a 100 reply
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/158 -F name=daniel
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
^Content-Type: multipart/form-data.*
^---------------------------.*
</strip>
<protocol>
POST /158 HTTP/1.1
User-Agent: curl/7.11.2-CVS (i686-pc-linux-gnu) libcurl/7.11.2-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 145
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------4f12fcdaa3bc

------------------------------4f12fcdaa3bc
Content-Disposition: form-data; name="name"

daniel
------------------------------4f12fcdaa3bc--
</protocol>
<errorcode>
52
</errorcode>
</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>`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 22:27:54 +08:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 100 Continue swsclose`
			`Silly-header: yeeeees`

			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP multipart formpost with only a 100 reply`
			`</name>`
			`<command>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 16:08:38 +08:00			`http://%HOSTIP:%HTTPPORT/158 -F name=daniel`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 22:27:54 +08:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`^Content-Type: multipart/form-data.*`
			`^---------------------------.*`
			`</strip>`
			`<protocol>`
			`POST /158 HTTP/1.1`
			`User-Agent: curl/7.11.2-CVS (i686-pc-linux-gnu) libcurl/7.11.2-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 22:27:54 +08:00			`Accept: /`
			`Content-Length: 145`
			`Expect: 100-continue`
			`Content-Type: multipart/form-data; boundary=----------------------------4f12fcdaa3bc`

			`------------------------------4f12fcdaa3bc`
			`Content-Disposition: form-data; name="name"`

			`daniel`
			`------------------------------4f12fcdaa3bc--`
			`</protocol>`
			`<errorcode>`
			`52`
			`</errorcode>`
			`</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>`