curl/tests/data/test510

<testcase>
<info>
<keywords>
HTTP
HTTP POST
chunked Transfer-Encoding
</keywords>
</info>

#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Connection: close
Content-Type: text/html

hello
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
# tool is what to use instead of 'curl'
<tool>
lib510
</tool>

 <name>
send HTTP POST using read callback, using chunked transfer-encoding
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/510
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
POST /510 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Transfer-Encoding: chunked
Content-Type: application/x-www-form-urlencoded
Expect: 100-continue

3
one
3
two
5
three
1d
and a final longer crap: four
0

</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`
tests: added missing keywords "chunked Transfer-Encoding" 2017-05-13 16:35:15 -04:00			`chunked Transfer-Encoding`
tests: add keywords for a couple of HTTP tests 2012-11-19 11:54:52 -05:00			`</keywords>`
			`</info>`

added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`#`
			`# Server-side`
			`<reply>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-01-31 18:58:58 -05:00			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake swsclose`
			`Connection: close`
			`Content-Type: text/html`

added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`hello`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib510`
			`</tool>`

			`<name>`
			`send HTTP POST using read callback, using chunked transfer-encoding`
			`</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/510`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`POST /510 HTTP/1.1`
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: /`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`Transfer-Encoding: chunked`
			`Content-Type: application/x-www-form-urlencoded`
- Martin Storsjo made libcurl use the Expect: 100-continue header for posts with unknown size. Previously it was only used for posts with a known size larger than 1024 bytes. 2009-12-07 15:25:17 -05:00			`Expect: 100-continue`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00
			`3`
stricter newline policy 2004-11-29 07:01:07 -05:00			`one`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`3`
stricter newline policy 2004-11-29 07:01:07 -05:00			`two`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`5`
stricter newline policy 2004-11-29 07:01:07 -05:00			`three`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`1d`
stricter newline policy 2004-11-29 07:01:07 -05:00			`and a final longer crap: four`
added test 510, callback-based POST using chunked encoding 2004-01-30 04:25:45 -05:00			`0`

			`</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>`