curl/tests/data/test260

<testcase>
<info>
<keywords>
HTTP
HTTP GET
</keywords>
</info>

#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 6
Connection: close
Content-Type: text/html
Funny-head: yesyes

-foo-
</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP GET URL without slash but with questionmark
 </name>
 <command>
"http://%HOSTIP:%HTTPPORT?260"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /?260 HTTP/1.1
Host: 127.0.0.1:%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-23 10:25:56 +08:00			`<testcase>`
Bug report #1204435 identified a problem with malformed URLs like "http://somehost?data" as it added a slash too much in the request ("GET /?data/"...). Added test case 260 to verify. 2005-05-19 04:01:01 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`
			`Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 6`
			`Connection: close`
			`Content-Type: text/html`
			`Funny-head: yesyes`

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-23 10:25:56 +08:00			`-foo-`
Bug report #1204435 identified a problem with malformed URLs like "http://somehost?data" as it added a slash too much in the request ("GET /?data/"...). Added test case 260 to verify. 2005-05-19 04:01:01 +08:00			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP GET URL without slash but with questionmark`
			`</name>`
			`<command>`
			`"http://%HOSTIP:%HTTPPORT?260"`
			`</command>`
			`</client>`

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

			`</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-23 10:25:56 +08:00			`</testcase>`