curl/tests/data/test503

<testcase>
# 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 127.0.0.1:%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 127.0.0.1:%HTTPSPORT HTTP/1.0
Host: 127.0.0.1:%HTTPSPORT
Proxy-Authorization: Basic dGVzdDppbmc=
Proxy-Connection: Keep-Alive

GET /503 HTTP/1.1
Authorization: Basic dGVzdDppbmc=
Host: 127.0.0.1:%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-22 21:25:56 -05:00			`<testcase>`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`# Server-side`
			`<reply>`
			`<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 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>`
Dan Fandrich's fix to use 127.0.0.1 instead of localhost to not depend on it resolving nicely 2004-09-22 14:21:45 -04:00			`http://%HOSTIP:%HTTPSPORT/503 127.0.0.1:%HTTPPORT`
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>`
			`<protocol>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 04:08:38 -04:00			`CONNECT 127.0.0.1:%HTTPSPORT HTTP/1.0`
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			`Host: 127.0.0.1:%HTTPSPORT`
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
			`GET /503 HTTP/1.1`
			`Authorization: Basic dGVzdDppbmc=`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 04:08:38 -04:00			`Host: 127.0.0.1:%HTTPSPORT`
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
			`</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>`