curl/tests/data/test1505

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

<reply>
<data>
HTTP/1.1 200 OK
Date: Tue, 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>
<tool>
lib1505
</tool>
 <name>
HTTP multi with CURLOPT_RESOLVE, cleanup sequence PB
 </name>
 <command>
http://google.com:%HTTPPORT/1505 %HTTPPORT %HOSTIP
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /1505 HTTP/1.1
Host: google.com:%HTTPPORT
Accept: */*

</protocol>
</verify>
</testcase>
test 1504 and 1505: same as 1502 but with different cleanup sequences 2012-12-24 08:04:34 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`multi`
			`CURLOPT_RESOLVE`
			`</keywords>`
			`</info>`

			`<reply>`
			`<data>`
testsuite: changed HTTP and RTSP header line-endings to CRLF According to RFC 2616 and RFC 2326 individual protocol elements, like headers and except the actual content, are terminated by using CRLF. Therefore the test data files for these protocols need to contain mixed line-endings if the actual protocol elements use CRLF while the file uses LF. 2014-01-31 18:52:08 -05:00			`HTTP/1.1 200 OK`
tests: fixup several tests missing CRs and modified %hostip lib556/test556: use a real HTTP version to make test reuse more convenient make sure the weekday in Date headers matches the date test61: replace stray "^M" (5e 4d) at the end of a cookie with a '^M' (0d) Gets the test working with external proxies like Privoxy again. Closes #6463 2020-02-28 09:00:03 -05:00			`Date: Tue, 09 Nov 2010 14:49:00 GMT`
testsuite: changed HTTP and RTSP header line-endings to CRLF According to RFC 2616 and RFC 2326 individual protocol elements, like headers and except the actual content, are terminated by using CRLF. Therefore the test data files for these protocols need to contain mixed line-endings if the actual protocol elements use CRLF while the file uses LF. 2014-01-31 18:52:08 -05:00			`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`

test 1504 and 1505: same as 1502 but with different cleanup sequences 2012-12-24 08:04:34 -05:00			`-foo-`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<tool>`
			`lib1505`
			`</tool>`
			`<name>`
			`HTTP multi with CURLOPT_RESOLVE, cleanup sequence PB`
			`</name>`
			`<command>`
			`http://google.com:%HTTPPORT/1505 %HTTPPORT %HOSTIP`
			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /1505 HTTP/1.1`
			`Host: google.com:%HTTPPORT`
			`Accept: /`

			`</protocol>`
			`</verify>`
			`</testcase>`