curl/tests/data/test1503

<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>
lib%TESTNUMBER
</tool>
 <name>
HTTP multi with CURLOPT_RESOLVE, cleanup sequence PA
 </name>
 <command>
http://google.com:%HTTPPORT/%TESTNUMBER %HTTPPORT %HOSTIP
</command>
</client>

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

</protocol>
</verify>
</testcase>
test 1503: same as 1502 but with a different cleanup sequence 2012-12-24 04:33:26 +08: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-02-01 07:52:08 +08: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 22:00:03 +08: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-02-01 07:52:08 +08: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 1503: same as 1502 but with a different cleanup sequence 2012-12-24 04:33:26 +08:00			`-foo-`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<tool>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`lib%TESTNUMBER`
test 1503: same as 1502 but with a different cleanup sequence 2012-12-24 04:33:26 +08:00			`</tool>`
			`<name>`
			`HTTP multi with CURLOPT_RESOLVE, cleanup sequence PA`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`http://google.com:%HTTPPORT/%TESTNUMBER %HTTPPORT %HOSTIP`
test 1503: same as 1502 but with a different cleanup sequence 2012-12-24 04:33:26 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`GET /%TESTNUMBER HTTP/1.1`
test 1503: same as 1502 but with a different cleanup sequence 2012-12-24 04:33:26 +08:00			`Host: google.com:%HTTPPORT`
			`Accept: /`

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