curl/tests/data/test9

<testcase>
<info>
<keywords>
HTTP
HTTP FORMPOST
HTTP file upload
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.0 200 OK swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake

blablabla

</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP RFC1867-type formposting
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/9 -F name=daniel -F tool=curl -F file=@log/test9.txt
</command>
# We create this file before the command is invoked!
<file name="log/test9.txt">
foo-
This is a moo-
bar
</file>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^(User-Agent:|Content-Type: multipart/form-data;|------------).*
</strip>
<protocol>
POST /we/want/9 HTTP/1.1
User-Agent: curl/7.10.4 (i686-pc-linux-gnu) libcurl/7.10.4 OpenSSL/0.9.7a ipv6 zlib/1.1.3
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 407
Content-Type: multipart/form-data; boundary=----------------------------9ef8d6205763

------------------------------9ef8d6205763
Content-Disposition: form-data; name="name"

daniel
------------------------------9ef8d6205763
Content-Disposition: form-data; name="tool"

curl
------------------------------9ef8d6205763
Content-Disposition: form-data; name="file"; filename="test9.txt"
Content-Type: text/plain

foo-
This is a moo-
bar

------------------------------9ef8d6205763--
</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-22 21:25:56 -05:00			`<testcase>`
keywords added 2005-04-15 20:00:35 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP FORMPOST`
			`HTTP file upload`
			`</keywords>`
			`</info>`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`# Server-side`
			`<reply>`
			`<data>`
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. 2006-11-25 08:32:04 -05:00			`HTTP/1.0 200 OK swsclose`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`

			`blablabla`

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

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`http`
			`</server>`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`<name>`
			`HTTP RFC1867-type formposting`
			`</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 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/we/want/9 -F name=daniel -F tool=curl -F file=@log/test9.txt`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`</command>`
			`# We create this file before the command is invoked!`
			`<file name="log/test9.txt">`
			`foo-`
			`This is a moo-`
			`bar`
			`</file>`
minor format fix 2004-04-23 04:40:20 -04:00			`</client>`
test case converted to the new file format 2001-05-28 08:30:21 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`^(User-Agent:\|Content-Type: multipart/form-data;\|------------).*`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`</strip>`
			`<protocol>`
			`POST /we/want/9 HTTP/1.1`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`User-Agent: curl/7.10.4 (i686-pc-linux-gnu) libcurl/7.10.4 OpenSSL/0.9.7a ipv6 zlib/1.1.3`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
- Based on Fedor Karpelevitch's formpost path basename patch, file parts in formposts no longer include the path part. If you _really_ want them, you must provide your preferred full file name with CURLFORM_FILENAME. Added detection for libgen.h and basename() to configure. My custom basename() replacement function for systems without it, might be a bit too naive... Updated 6 test cases to make them work with the stripped paths. 2004-10-01 02:36:11 -04:00			`Content-Length: 407`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`Content-Type: multipart/form-data; boundary=----------------------------9ef8d6205763`
test case converted to the new file format 2001-05-28 08:30:21 -04:00
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`------------------------------9ef8d6205763`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`Content-Disposition: form-data; name="name"`

			`daniel`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`------------------------------9ef8d6205763`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`Content-Disposition: form-data; name="tool"`

			`curl`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`------------------------------9ef8d6205763`
- Based on Fedor Karpelevitch's formpost path basename patch, file parts in formposts no longer include the path part. If you _really_ want them, you must provide your preferred full file name with CURLFORM_FILENAME. Added detection for libgen.h and basename() to configure. My custom basename() replacement function for systems without it, might be a bit too naive... Updated 6 test cases to make them work with the stripped paths. 2004-10-01 02:36:11 -04:00			`Content-Disposition: form-data; name="file"; filename="test9.txt"`
test case converted to the new file format 2001-05-28 08:30:21 -04:00			`Content-Type: text/plain`

			`foo-`
			`This is a moo-`
			`bar`

adjusted the formpost testcases to the new boundary string construction 2003-04-04 07:30:35 -05:00			`------------------------------9ef8d6205763--`
test case converted to the new file format 2001-05-28 08:30:21 -04: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-22 21:25:56 -05:00			`</testcase>`