curl/tests/data/test560

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

#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Length: 7

MooMoo
</data>
</reply>

#
# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
<tool>
lib%TESTNUMBER
</tool>
 <name>
simple HTTPS GET with multi interface
 </name>
 <command>
https://%HOSTIP:%HTTPSPORT/%TESTNUMBER
</command>
</client>

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

</protocol>
</verify>
</testcase>
Added test case 560: This test was added after the HTTPS-using-multi-interface with OpenSSL regression of 7.19.1 to hopefully prevent this embarassing mistake from appearing again... Unfortunately the bug wasn't triggered by this test, which presumably is because the connect to a local server is too fast/different compared to the real/distant servers we saw the bug happen with. 2008-11-12 05:59:25 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTPS`
			`HTTP GET`
			`multi`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<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`
			`Content-Length: 7`

Added test case 560: This test was added after the HTTPS-using-multi-interface with OpenSSL regression of 7.19.1 to hopefully prevent this embarassing mistake from appearing again... Unfortunately the bug wasn't triggered by this test, which presumably is because the connect to a local server is too fast/different compared to the real/distant servers we saw the bug happen with. 2008-11-12 05:59:25 +08:00			`MooMoo`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<features>`
			`SSL`
			`</features>`
			`<server>`
			`https`
			`</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`
Added test case 560: This test was added after the HTTPS-using-multi-interface with OpenSSL regression of 7.19.1 to hopefully prevent this embarassing mistake from appearing again... Unfortunately the bug wasn't triggered by this test, which presumably is because the connect to a local server is too fast/different compared to the real/distant servers we saw the bug happen with. 2008-11-12 05:59:25 +08:00			`</tool>`
			`<name>`
			`simple HTTPS GET with multi interface`
			`</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			`https://%HOSTIP:%HTTPSPORT/%TESTNUMBER`
Added test case 560: This test was added after the HTTPS-using-multi-interface with OpenSSL regression of 7.19.1 to hopefully prevent this embarassing mistake from appearing again... Unfortunately the bug wasn't triggered by this test, which presumably is because the connect to a local server is too fast/different compared to the real/distant servers we saw the bug happen with. 2008-11-12 05:59:25 +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`
Added test case 560: This test was added after the HTTPS-using-multi-interface with OpenSSL regression of 7.19.1 to hopefully prevent this embarassing mistake from appearing again... Unfortunately the bug wasn't triggered by this test, which presumably is because the connect to a local server is too fast/different compared to the real/distant servers we saw the bug happen with. 2008-11-12 05:59:25 +08:00			`Host: %HOSTIP:%HTTPSPORT`
			`Accept: /`

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