curl/tests/data/test549

<testcase>
<info>
<keywords>
FTP
CURLOPT_PROXY_TRANSFER_MODE
CURLOPT_PROXY
HTTP 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>
<features>
ftp
</features>
<tool>
lib549
</tool>
 <name>
FTP RETR over proxy with CURLOPT_PROXY_TRANSFER_MODE
 </name>
# first URL then proxy
 <command>
ftp://www.example.com/moo/549 http://%HOSTIP:%HTTPPORT 
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET ftp://www.example.com/moo/549;type=i HTTP/1.1
Host: www.example.com:21
Accept: */*
Proxy-Connection: Keep-Alive

</protocol>
<stdout>
hello
</stdout>
</verify>
</testcase>
add test 549 and 550 2007-12-08 17:53:28 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`FTP`
			`CURLOPT_PROXY_TRANSFER_MODE`
			`CURLOPT_PROXY`
Added "HTTP proxy" and "proxytunnel" keywords where applicable 2008-09-29 18:44:04 -04:00			`HTTP proxy`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`</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`

add test 549 and 550 2007-12-08 17:53:28 -05:00			`hello`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
Added missing <features> 2007-12-13 20:09:45 -05:00			`<features>`
			`ftp`
			`</features>`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`<tool>`
			`lib549`
			`</tool>`
			`<name>`
Fixed typo in test title 2007-12-13 20:05:30 -05:00			`FTP RETR over proxy with CURLOPT_PROXY_TRANSFER_MODE`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`</name>`
			`# first URL then proxy`
			`<command>`
tests: phase out haxx.se Instead of using haxx.se as a fixed magic host name in lots of tests, this is a first step to move toward the generic example.com host instead. 2011-03-09 17:04:38 -05:00			`ftp://www.example.com/moo/549 http://%HOSTIP:%HTTPPORT`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
tests: phase out haxx.se Instead of using haxx.se as a fixed magic host name in lots of tests, this is a first step to move toward the generic example.com host instead. 2011-03-09 17:04:38 -05:00			`GET ftp://www.example.com/moo/549;type=i HTTP/1.1`
			`Host: www.example.com:21`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`Accept: /`
			`Proxy-Connection: Keep-Alive`

			`</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>`
add test 549 and 550 2007-12-08 17:53:28 -05:00			`hello`
			`</stdout>`
			`</verify>`
			`</testcase>`