curl/tests/data/test95

<testcase>
<info>
<keywords>
HTTP
HTTP POST
HTTP CONNECT
proxytunnel
</keywords>
</info>

#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes
Content-Length: 9

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

HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes
Content-Length: 9

contents
</datacheck>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP over proxytunnel using POST
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/that/page/95 -p -x %HOSTIP:%HTTPPORT -d "datatopost=ohthatsfunyesyes"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol nonewline="yes">
CONNECT %HOSTIP:%HTTPPORT HTTP/1.1
User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3
Host: %HOSTIP:%HTTPPORT
Proxy-Connection: Keep-Alive

POST /we/want/that/page/95 HTTP/1.1
User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 27
Content-Type: application/x-www-form-urlencoded

datatopost=ohthatsfunyesyes
</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 10:25:56 +08:00			`<testcase>`
keyword update 2005-04-27 17:59:47 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP POST`
Added HTTP CONNECT keywords 2008-08-12 07:16:48 +08:00			`HTTP CONNECT`
keyword update 2005-04-27 17:59:47 +08:00			`proxytunnel`
			`</keywords>`
			`</info>`
Added HTTP CONNECT keywords 2008-08-12 07:16:48 +08:00
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake swsclose`
			`Content-Type: text/html`
			`Funny-head: yesyes`
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. 2006-11-25 21:32:04 +08:00			`Content-Length: 9`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00
			`contents`
			`</data>`
CONNECT response headers are now passed back as "regular" headers 2004-01-27 20:54:22 +08:00			`<datacheck>`
stricter newline policy 2004-11-29 20:01:07 +08:00			`HTTP/1.1 200 Mighty fine indeed`

CONNECT response headers are now passed back as "regular" headers 2004-01-27 20:54:22 +08:00			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake swsclose`
			`Content-Type: text/html`
			`Funny-head: yesyes`
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. 2006-11-25 21:32:04 +08:00			`Content-Length: 9`
CONNECT response headers are now passed back as "regular" headers 2004-01-27 20:54:22 +08:00
			`contents`
			`</datacheck>`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP over proxytunnel using POST`
			`</name>`
			`<command>`
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 16:08:38 +08:00			`http://%HOSTIP:%HTTPPORT/we/want/that/page/95 -p -x %HOSTIP:%HTTPPORT -d "datatopost=ohthatsfunyesyes"`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-26 05:45:03 +08:00			`</client>`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
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 10:25:56 +08:00			`<protocol nonewline="yes">`
- 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-03 00:19:23 +08:00			`CONNECT %HOSTIP:%HTTPPORT HTTP/1.1`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00			`User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
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 17:52:59 +08:00			`Proxy-Connection: Keep-Alive`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00
			`POST /we/want/that/page/95 HTTP/1.1`
			`User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 20:46:41 +08:00			`Accept: /`
test 95 added, verifies my fix for bug report #848371 2003-11-25 17:06:33 +08:00			`Content-Length: 27`
			`Content-Type: application/x-www-form-urlencoded`

			`datatopost=ohthatsfunyesyes`
			`</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 10:25:56 +08:00			`</testcase>`