curl/tests/data/test523

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP proxy
CURLOPT_PORT
CURLOPT_PROXY
</keywords>
</info>

#
# Server-side
<reply>
<data nocheck="yes">
HTTP/1.1 200 OK swsclose
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

hello
</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
<tool>
lib523
</tool>
 <name>
HTTP GET with proxy and CURLOPT_PORT
 </name>
# first URL then proxy
 <command>
http://www.example.com:999/523 http://%HOSTIP:%HTTPPORT 
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET HTTP://www.example.com:19999/523 HTTP/1.1
Host: www.example.com:19999
Authorization: Basic eHh4Onl5eQ==
Accept: */*

</protocol>
<stdout>
hello
</stdout>
</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>`
added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
Added "HTTP proxy" and "proxytunnel" keywords where applicable 2008-09-29 18:44:04 -04:00			`HTTP proxy`
added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`CURLOPT_PORT`
			`CURLOPT_PROXY`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
Always use nocheck="yes" for consistency 2009-01-07 16:57:26 -05:00			`<data nocheck="yes">`
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 swsclose`
			`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`

added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`hello`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<tool>`
			`lib523`
			`</tool>`
			`<name>`
			`HTTP GET with proxy and CURLOPT_PORT`
			`</name>`
			`# first URL then proxy`
			`<command>`
test523: avoid using haxx.se ... since search engines find what they think is a URL in this, they hammer www.haxx.se on this port! 2011-03-09 08:10:44 -05:00			`http://www.example.com:999/523 http://%HOSTIP:%HTTPPORT`
added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
test523: avoid using haxx.se ... since search engines find what they think is a URL in this, they hammer www.haxx.se on this port! 2011-03-09 08:10:44 -05:00			`GET HTTP://www.example.com:19999/523 HTTP/1.1`
			`Host: www.example.com:19999`
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan 2015-03-11 19:50:46 -04:00			`Authorization: Basic eHh4Onl5eQ==`
added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`Accept: /`

			`</protocol>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-01-31 18:58:58 -05:00			`<stdout>`
added CURLOPT_PORT test when using proxy 2005-04-19 04:10:04 -04:00			`hello`
			`</stdout>`
			`</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>`