curl/tests/data/test60

# 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" < log/60.txt
</command>
<file name="log/60.txt">
more than one byte
</file>
</client>

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

13
more than one byte

0

</protocol>
</verify>
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 16:09:58 +04:00			`# Server-side`
			`<reply>`
			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-20 03:57:08 +04:00			`HTTP/1.0 200 OK swsclose`
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 16:09:58 +04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`

			`blablabla`

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

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-05-01 00: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 16:09:58 +04:00			`<name>`
			`HTTP PUT from stdin with wrong content-length`
			`</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 12:08:38 +04:00			`http://%HOSTIP:%HTTPPORT/bzz/60 -T - -H "Content-Length: 1" < log/60.txt`
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 16:09:58 +04:00			`</command>`
			`<file name="log/60.txt">`
			`more than one byte`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`PUT /bzz/60 HTTP/1.1`
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 12:08:38 +04:00			`Host: 127.0.0.1:%HTTPPORT`
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 16:09:58 +04:00			`Pragma: no-cache`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 15:46:41 +03: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 16:09:58 +04:00			`Transfer-Encoding: chunked`
			`Content-Length: 1`
issue 12 fix 2004-03-05 15:54:18 +03: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 16:09:58 +04:00
			`13`
			`more than one byte`

			`0`
adjusted to the corrected chunked transfer-encoding extra trailing CRLF 2004-01-29 10:43:56 +03: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 16:09:58 +04:00			`</protocol>`
			`</verify>`