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>
<servercmd>
connection-monitor
</servercmd>
<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
http-proxy
</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:%HTTPPORT/503 %HOSTIP:%PROXYPORT
</command>
<file name="log/test503.txt">
foo
   bar
bar
   foo
moo
</file>
</client>

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

</proxy>
<protocol>
GET /503 HTTP/1.1
Authorization: Basic dGVzdDppbmc=
Host: %HOSTIP:%HTTPPORT
Accept: */*

[DISCONNECT]
</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-22 21:25:56 -05:00			`<testcase>`
Added HTTP CONNECT keywords 2008-08-11 19: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 11:17:27 -05:00			`# Server-side`
			`<reply>`
sws: add 'connection-monitor' command support Using this, the server will output in the protocol log when the connection gets disconnected and thus we will verify correctly in the test cases that the connection doesn't get closed prematurely. This is important for example NTLM to work. Documentation added to FILEFORMAT, test 503 updated to use this. 2012-07-05 03:31:04 -04:00			`<servercmd>`
			`connection-monitor`
			`</servercmd>`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`HTTP/1.1 200 OK swsclose`
test case 503 entered the dir 2002-12-13 11:17:27 -05: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 07:54:22 -05:00			`<datacheck>`
stricter newline policy 2004-11-29 07:01:07 -05:00			`HTTP/1.1 200 Mighty fine indeed`

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

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

			`# Client-side`
			`<client>`
			`<server>`
mistake, this only requires http 2002-12-16 09:50:10 -05:00			`http`
test proxy supports CONNECT There's a new 'http-proxy' server for tests that runs on a separate port and lets clients do HTTP CONNECT to other ports on the same host to allow us to test HTTP "tunneling" properly. Test cases now have a <proxy> section in <verify> to check that the proxy protocol part matches correctly. Test case 80, 83, 95, 275, 503 and 1078 have been converted. Test 1316 was added. 2011-12-17 17:47:22 -05:00			`http-proxy`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib503`
			`</tool>`

			`<name>`
better name, it isn't https 2003-10-24 16:39:39 -04:00			`simple multi http:// through proxytunnel with authentication info`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`</name>`
			`<command>`
test proxy supports CONNECT There's a new 'http-proxy' server for tests that runs on a separate port and lets clients do HTTP CONNECT to other ports on the same host to allow us to test HTTP "tunneling" properly. Test cases now have a <proxy> section in <verify> to check that the proxy protocol part matches correctly. Test case 80, 83, 95, 275, 503 and 1078 have been converted. Test 1316 was added. 2011-12-17 17:47:22 -05:00			`http://%HOSTIP:%HTTPPORT/503 %HOSTIP:%PROXYPORT`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`</command>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`<file name="log/test503.txt">`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`foo`
			`bar`
			`bar`
			`foo`
			`moo`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
test proxy supports CONNECT There's a new 'http-proxy' server for tests that runs on a separate port and lets clients do HTTP CONNECT to other ports on the same host to allow us to test HTTP "tunneling" properly. Test cases now have a <proxy> section in <verify> to check that the proxy protocol part matches correctly. Test case 80, 83, 95, 275, 503 and 1078 have been converted. Test 1316 was added. 2011-12-17 17:47:22 -05:00			`<proxy>`
			`CONNECT %HOSTIP:%HTTPPORT HTTP/1.1`
			`Host: %HOSTIP:%HTTPPORT`
General HTTP authentication cleanup and fixes 2004-05-04 03: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 05:52:59 -04:00			`Proxy-Connection: Keep-Alive`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00
test proxy supports CONNECT There's a new 'http-proxy' server for tests that runs on a separate port and lets clients do HTTP CONNECT to other ports on the same host to allow us to test HTTP "tunneling" properly. Test cases now have a <proxy> section in <verify> to check that the proxy protocol part matches correctly. Test case 80, 83, 95, 275, 503 and 1078 have been converted. Test 1316 was added. 2011-12-17 17:47:22 -05:00			`</proxy>`
			`<protocol>`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`GET /503 HTTP/1.1`
			`Authorization: Basic dGVzdDppbmc=`
test proxy supports CONNECT There's a new 'http-proxy' server for tests that runs on a separate port and lets clients do HTTP CONNECT to other ports on the same host to allow us to test HTTP "tunneling" properly. Test cases now have a <proxy> section in <verify> to check that the proxy protocol part matches correctly. Test case 80, 83, 95, 275, 503 and 1078 have been converted. Test 1316 was added. 2011-12-17 17:47:22 -05:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00
tests: use connection-monitor and verify results Test 1008 and 206 don't show the disconnect since it happens when SWS awaits a new request, but 503 does and so the verify section needs that string added. 2012-07-05 05:20:18 -04:00			`[DISCONNECT]`
test case 503 entered the dir 2002-12-13 11:17:27 -05: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-22 21:25:56 -05:00			`</testcase>`