curl/tests/data/test544

<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: 3

OK
</data>
</reply>

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

 <name>
HTTP POST text data using CURLOPT_COPYPOSTFIELDS
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/544
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol nonewline="yes">
POST /544 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 4
Content-Type: application/x-www-form-urlencoded

This
</protocol>
</verify>
</testcase>
Allow test server to handle binary POSTs. Tests 35, 544 545 added: binary data POSTs. 2007-10-25 15:40:05 -04: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>`

Allow test server to handle binary POSTs. Tests 35, 544 545 added: binary data POSTs. 2007-10-25 15:40:05 -04: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 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`
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			`Server: test-server/fake`
			`Content-Length: 3`

Allow test server to handle binary POSTs. Tests 35, 544 545 added: binary data POSTs. 2007-10-25 15:40:05 -04:00			`OK`
			`</data>`
			`</reply>`

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

			`<name>`
			`HTTP POST text data using CURLOPT_COPYPOSTFIELDS`
			`</name>`
			`<command>`
			`http://%HOSTIP:%HTTPPORT/544`
			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol nonewline="yes">`
			`POST /544 HTTP/1.1`
			`Host: %HOSTIP:%HTTPPORT`
			`Accept: /`
			`Content-Length: 4`
			`Content-Type: application/x-www-form-urlencoded`

			`This`
			`</protocol>`
			`</verify>`
			`</testcase>`