curl/tests/data/test59

<testcase>
<info>
<keywords>
HTTP
HTTP GET
</keywords>
</info>
#
# Server-side
<reply name="1">
<data>
HTTP/1.0 200 OK swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake

hej 
</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP URL with slash but with "parameter"
 </name>
 <command>
"http://%HOSTIP:%HTTPPORT?mooo/59"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /?mooo/59 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*

</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 GET`
			`</keywords>`
			`</info>`
verify the new url parser fix 2003-04-11 12:22:27 -04:00			`#`
			`# Server-side`
			`<reply name="1">`
			`<data>`
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. 2006-11-25 08:32:04 -05:00			`HTTP/1.0 200 OK swsclose`
verify the new url parser fix 2003-04-11 12:22:27 -04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`

			`hej`
			`</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>`
verify the new url parser fix 2003-04-11 12:22:27 -04:00			`<name>`
			`HTTP URL with slash but with "parameter"`
			`</name>`
			`<command>`
use quotes to make gdb usage on this easier 2004-10-14 09:44:16 -04:00			`"http://%HOSTIP:%HTTPPORT?mooo/59"`
verify the new url parser fix 2003-04-11 12:22:27 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /?mooo/59 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: /`
verify the new url parser fix 2003-04-11 12:22:27 -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>`