curl/tests/data/test186

<testcase>
<info>
<keywords>
HTTP
HTTP POST
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.1 200 OK swsclose
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Length: 11

blablabla

</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP RFC1867-type formposting with types on text fields
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -F "name=daniel;type=moo/foo" -F "html= <body>hello</body>;type=text/html;charset=verymoo"
</command>
# We create this file before the command is invoked!
</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: 320
Content-Type: multipart/form-data; boundary=----------------------------212d9006ceb5

------------------------------212d9006ceb5
Content-Disposition: form-data; name="name"
Content-Type: moo/foo

daniel
------------------------------212d9006ceb5
Content-Disposition: form-data; name="html"
Content-Type: text/html;charset=verymoo

<body>hello</body>
------------------------------212d9006ceb5--
</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>`
tests: add keywords for a couple of HTTP tests 2012-11-19 11:54:52 -05:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP POST`
			`</keywords>`
			`</info>`

fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 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 09:00:03 -05:00			`Date: Tue, 09 Nov 2010 14:49:00 GMT`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`Server: test-server/fake`
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			`Content-Length: 11`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00
			`blablabla`

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

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP RFC1867-type formposting with types on text fields`
			`</name>`
			`<command>`
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-12 11:38:26 -05:00			`http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -F "name=daniel;type=moo/foo" -F "html= <body>hello</body>;type=text/html;charset=verymoo"`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`</command>`
			`# We create this file before the command is invoked!`
			`</client>`

			`# 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 07:45:24 -04:00			`^(Content-Type: multipart/form-data;\|------------).*`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04: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-12 11:38:26 -05:00			`POST /we/want/%TESTNUMBER HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04: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 07:45:24 -04:00			`User-Agent: curl/%VERSION`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`Accept: /`
mime: tests and examples. Additional mime-specific tests. Existing tests updated to reflect small differences (Expect: 100-continue, data size change due to empty lines, etc). Option -F headers= keyword added to tests. test1135 disabled until the entry point order change is resolved. New example smtp-mime. Examples postit2 and multi-post converted from form API to mime API. 2017-09-02 14:08:45 -04:00			`Content-Length: 320`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`Content-Type: multipart/form-data; boundary=----------------------------212d9006ceb5`

			`------------------------------212d9006ceb5`
			`Content-Disposition: form-data; name="name"`
			`Content-Type: moo/foo`

			`daniel`
			`------------------------------212d9006ceb5`
			`Content-Disposition: form-data; name="html"`
cmdline: make -F type= accept ;charset= The -F option allows some custom parameters within the given string, and those strings are separated with semicolons. You can for example specify "name=daniel;type=text/plain" to set content-type for the field. However, the use of semicolons like that made it not work fine if you specified one within the content-type, like for: "name=daniel;type=text/plain;charset=UTF-8" ... as the second one would be seen as a separator and "charset" is no parameter curl knows anything about so it was just silently discarded. The new logic now checks if the semicolon and following keyword looks like a parameter it knows about and if it isn't it is assumed to be meant to be used within the content-type string itself. I modified test case 186 to verify that this works as intended. Reported by: Larry Stone Bug: http://curl.haxx.se/bug/view.cgi?id=3048988 2010-08-20 18:21:24 -04:00			`Content-Type: text/html;charset=verymoo`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00
mime: tests and examples. Additional mime-specific tests. Existing tests updated to reflect small differences (Expect: 100-continue, data size change due to empty lines, etc). Option -F headers= keyword added to tests. test1135 disabled until the entry point order change is resolved. New example smtp-mime. Examples postit2 and multi-post converted from form API to mime API. 2017-09-02 14:08:45 -04:00			`<body>hello</body>`
fixed -F to support setting type= even on parts that aren't file-uploads 2004-09-10 17:47:52 -04:00			`------------------------------212d9006ceb5--`
			`</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>`