curl/tests/data/test503

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP CONNECT
HTTP proxy
HTTP proxy Basic auth
proxytunnel
multi
</keywords>
</info>

# Server-side
<reply>
<data>
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"

</data>
<datacheck>
HTTP/1.1 200 Mighty fine indeed

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"

</datacheck>
</reply>

# Client-side
<client>
<server>
http
</server>
# tool is what to use instead of 'curl'
<tool>
lib503
</tool>

 <name>
simple multi http:// through proxytunnel with authentication info
 </name>
 <command>
http://%HOSTIP:%HTTPSPORT/503 %HOSTIP:%HTTPPORT
</command>
<file name="log/test503.txt">
foo
   bar
bar
   foo
moo
</file>
</client>

# Verify data after the test has been "shot"
<verify>
<protocol>
CONNECT %HOSTIP:%HTTPSPORT HTTP/1.1
Host: %HOSTIP:%HTTPSPORT
Proxy-Authorization: Basic dGVzdDppbmc=
Proxy-Connection: Keep-Alive

GET /503 HTTP/1.1
Authorization: Basic dGVzdDppbmc=
Host: %HOSTIP:%HTTPSPORT
Accept: */*

</protocol>
</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-23 05:25:56 +03:00			`<testcase>`
Added HTTP CONNECT keywords 2008-08-12 03:16:48 +04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP CONNECT`
			`HTTP proxy`
			`HTTP proxy Basic auth`
			`proxytunnel`
			`multi`
			`</keywords>`
			`</info>`

test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`# Server-side`
			`<reply>`
			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-20 03:57:08 +04:00			`HTTP/1.1 200 OK swsclose`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`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"`

			`</data>`
CONNECT response headers are now passed back as "regular" headers 2004-01-27 15:54:22 +03:00			`<datacheck>`
stricter newline policy 2004-11-29 15:01:07 +03:00			`HTTP/1.1 200 Mighty fine indeed`

CONNECT response headers are now passed back as "regular" headers 2004-01-27 15:54:22 +03: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"`

			`</datacheck>`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
mistake, this only requires http 2002-12-16 17:50:10 +03:00			`http`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib503`
			`</tool>`

			`<name>`
better name, it isn't https 2003-10-25 00:39:39 +04:00			`simple multi http:// through proxytunnel with authentication info`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`</name>`
			`<command>`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 23:32:31 +04:00			`http://%HOSTIP:%HTTPSPORT/503 %HOSTIP:%HTTPPORT`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`</command>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-20 03:57:08 +04:00			`<file name="log/test503.txt">`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00			`foo`
			`bar`
			`bar`
			`foo`
			`moo`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
- Craig A West brought us: libcurl now defaults to do CONNECT with HTTP version 1.1 instead of 1.0 like before. This change also introduces the new proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0 option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0. I updated all test cases cases that use CONNECT and I tried to do some using --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run. 2009-02-02 19:19:23 +03:00			`CONNECT %HOSTIP:%HTTPSPORT HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 23:32:31 +04:00			`Host: %HOSTIP:%HTTPSPORT`
General HTTP authentication cleanup and fixes 2004-05-04 11:52:53 +04:00			`Proxy-Authorization: Basic dGVzdDppbmc=`
Modified the default HTTP headers used by libcurl: A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive" 2005-05-11 13:52:59 +04:00			`Proxy-Connection: Keep-Alive`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00
			`GET /503 HTTP/1.1`
			`Authorization: Basic dGVzdDppbmc=`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 23:32:31 +04:00			`Host: %HOSTIP:%HTTPSPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 15:46:41 +03:00			`Accept: /`
test case 503 entered the dir 2002-12-13 19:17:27 +03:00
			`</protocol>`
			`</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-23 05:25:56 +03:00			`</testcase>`