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: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake

blablabla

</data>
</reply>

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

# Verify data after the test has been "shot"
<verify>
<strip>
^(Content-Type: multipart/form-data;|------------).*
</strip>
<protocol>
POST /we/want/%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
Content-Length: 431
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-23 10:25:56 +08:00			`<testcase>`
keywords added 2005-04-16 08:00:35 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP FORMPOST`
			`HTTP file upload`
			`</keywords>`
			`</info>`
test case converted to the new file format 2001-05-28 20:30:21 +08: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 21:32:04 +08:00			`HTTP/1.0 200 OK swsclose`
tests: fixup several tests missing CRs and modified %hostip lib556/test556: use a real HTTP version to make test reuse more convenient make sure the weekday in Date headers matches the date test61: replace stray "^M" (5e 4d) at the end of a cookie with a '^M' (0d) Gets the test working with external proxies like Privoxy again. Closes #6463 2020-02-28 22:00:03 +08:00			`Date: Tue, 09 Nov 2010 14:49:00 GMT`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`Server: test-server/fake`

			`blablabla`

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

			`# Client-side`
			`<client>`
tests: skip mime/form tests when mime is not built-in Closes #9596 2022-09-26 21:38:41 +08:00			`<features>`
			`Mime`
			`</features>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-05-01 04:25:39 +08:00			`<server>`
			`http`
			`</server>`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`<name>`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`HTTP RFC1867-type formposting`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`</name>`
			`<command>`
tests: use %LOGDIR to refer to the log directory This will allow it be set dynamically. Ref: #10818 2023-03-29 09:20:54 +08:00			`http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -F name=daniel -F tool=curl -F file=@%LOGDIR/test%TESTNUMBER.txt`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`</command>`
			`# We create this file before the command is invoked!`
tests: use %LOGDIR to refer to the log directory This will allow it be set dynamically. Ref: #10818 2023-03-29 09:20:54 +08:00			`<file name="%LOGDIR/test%TESTNUMBER.txt">`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`foo-`
			`This is a moo-`
			`bar`
			`</file>`
minor format fix 2004-04-23 16:40:20 +08:00			`</client>`
test case converted to the new file format 2001-05-28 20:30:21 +08:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 19:45:24 +08:00			`^(Content-Type: multipart/form-data;\|------------).*`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`</strip>`
			`<protocol>`
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			`POST /we/want/%TESTNUMBER HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 19:45:24 +08:00			`User-Agent: curl/%VERSION`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 20:46:41 +08:00			`Accept: /`
misc: better random strings Generate alphanumerical random strings. Prior this change curl used to create random hex strings. This was mostly okay, but having alphanumerical random strings is better: The strings have more entropy in the same space. The MIME multipart boundary used to be mere 64-bits of randomness due to being 16 hex chars. With these changes the boundary is 22 alphanumerical chars, or little over 130 bits of randomness. Closes #11838 2023-09-12 18:51:21 +08:00			`Content-Length: 431`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 20:30:35 +08:00			`Content-Type: multipart/form-data; boundary=----------------------------9ef8d6205763`
test case converted to the new file format 2001-05-28 20:30:21 +08:00
adjusted the formpost testcases to the new boundary string construction 2003-04-04 20:30:35 +08:00			`------------------------------9ef8d6205763`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`Content-Disposition: form-data; name="name"`

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

			`curl`
adjusted the formpost testcases to the new boundary string construction 2003-04-04 20:30:35 +08: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 14:36:11 +08:00			`Content-Disposition: form-data; name="file"; filename="test9.txt"`
test case converted to the new file format 2001-05-28 20:30:21 +08:00			`Content-Type: text/plain`

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

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