curl/tests/data/test60

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

# Server-side
<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 PUT from stdin with wrong content-length
</name>
 <command>
http://%HOSTIP:%HTTPPORT/bzz/60 -T - -H "Content-Length: 1"
</command>
<stdin>
more than one byte
</stdin>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
PUT /bzz/60 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Transfer-Encoding: chunked
Content-Length: 1
Expect: 100-continue

13
more than one byte

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>`
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP PUT`
tests: added missing keywords "chunked Transfer-Encoding" 2017-05-13 16:35:15 -04:00			`chunked Transfer-Encoding`
keywords added 2005-04-22 17:59:08 -04:00			`</keywords>`
			`</info>`
Added test case 1068 to do a simple HTTP PUT from stdin 2008-08-27 22:03:54 -04:00
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`# Server-side`
			`<reply>`
			`<data>`
Fixed the XML syntax of a few test files. 2008-07-17 18:39:23 -04:00			`HTTP/1.0 200 OK swsclose`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`

Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`blablabla`

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

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`http`
			`</server>`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`<name>`
			`HTTP PUT from stdin with wrong content-length`
			`</name>`
			`<command>`
Added test case 1068 to do a simple HTTP PUT from stdin 2008-08-27 22:03:54 -04:00			`http://%HOSTIP:%HTTPPORT/bzz/60 -T - -H "Content-Length: 1"`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`</command>`
Added test case 1068 to do a simple HTTP PUT from stdin 2008-08-27 22:03:54 -04:00			`<stdin>`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`more than one byte`
Added test case 1068 to do a simple HTTP PUT from stdin 2008-08-27 22:03:54 -04:00			`</stdin>`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`PUT /bzz/60 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: /`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00			`Transfer-Encoding: chunked`
			`Content-Length: 1`
issue 12 fix 2004-03-05 07:54:18 -05:00			`Expect: 100-continue`
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04:00
			`13`
			`more than one byte`

			`0`
adjusted to the corrected chunked transfer-encoding extra trailing CRLF 2004-01-29 02:43:56 -05:00
Bryan Kemp's reported problems with curl and PUT from stdin and a faked content-length made me add test case 60, that does exactly this, but it seems to run fine... 2003-04-23 08:09:58 -04: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-22 21:25:56 -05:00			`</testcase>`