curl/tests/data/test181

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

<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 1.0 POST
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/181 --data-binary @log/test181.txt --http1.0
</command>
<file name="log/test181.txt">
Weird
     file
         to
   upload
for
   testing
the
   POST
      feature
</file>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
POST /we/want/181 HTTP/1.0
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 79
Content-Type: application/x-www-form-urlencoded

Weird
     file
         to
   upload
for
   testing
the
   POST
      feature
</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`
			`HTTP/1.0`
			`</keywords>`
			`</info>`

Roman Koifman pointed out that libcurl send Expect: 100-continue on POSTs and PUTs even when told to use HTTP 1.0, which is not correct. 2004-08-23 08:34:55 -04:00			`<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 1.0 POST`
			`</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/181 --data-binary @log/test181.txt --http1.0`
Roman Koifman pointed out that libcurl send Expect: 100-continue on POSTs and PUTs even when told to use HTTP 1.0, which is not correct. 2004-08-23 08:34:55 -04:00			`</command>`
			`<file name="log/test181.txt">`
			`Weird`
			`file`
			`to`
			`upload`
			`for`
			`testing`
			`the`
			`POST`
			`feature`
			`</file>`
Fixed some tag typos in the test data files. 2007-01-17 15:36:56 -05:00			`</client>`
Roman Koifman pointed out that libcurl send Expect: 100-continue on POSTs and PUTs even when told to use HTTP 1.0, which is not correct. 2004-08-23 08:34:55 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`POST /we/want/181 HTTP/1.0`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Roman Koifman pointed out that libcurl send Expect: 100-continue on POSTs and PUTs even when told to use HTTP 1.0, which is not correct. 2004-08-23 08:34:55 -04:00			`Accept: /`
			`Content-Length: 79`
			`Content-Type: application/x-www-form-urlencoded`

			`Weird`
			`file`
			`to`
			`upload`
			`for`
			`testing`
			`the`
			`POST`
			`feature`
			`</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>`