curl/tests/data/test80

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP CONNECT
HTTP Basic auth
HTTP proxy
HTTP proxy Basic auth
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 1.0 CONNECT with proxytunnel and host Basic authentication
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/that/page/80 -p --proxy1.0 %HOSTIP:%HTTPPORT --user iam:myself --proxy-user youare:yourself
</command>
</client>

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

GET /we/want/that/page/80 HTTP/1.1
Authorization: Basic aWFtOm15c2VsZg==
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: */*

</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>`
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP CONNECT`
			`HTTP Basic auth`
Added "HTTP proxy" and "proxytunnel" keywords where applicable 2008-09-29 18:44:04 -04:00			`HTTP proxy`
keywords added 2005-04-22 17:59:08 -04:00			`HTTP proxy Basic auth`
Added "HTTP proxy" and "proxytunnel" keywords where applicable 2008-09-29 18:44:04 -04:00			`proxytunnel`
keywords added 2005-04-22 17:59:08 -04:00			`</keywords>`
			`</info>`
Added "HTTP proxy" and "proxytunnel" keywords where applicable 2008-09-29 18:44:04 -04:00
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04: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 08:32:04 -05:00			`Content-Length: 9`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00
			`contents`
			`</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`
			`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 08:32:04 -05:00			`Content-Length: 9`
CONNECT response headers are now passed back as "regular" headers 2004-01-27 07:54:22 -05:00
			`contents`
			`</datacheck>`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
- 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 11:19:23 -05:00			`HTTP 1.0 CONNECT with proxytunnel and host Basic authentication`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00			`</name>`
			`<command>`
- 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 11:19:23 -05:00			`http://%HOSTIP:%HTTPPORT/we/want/that/page/80 -p --proxy1.0 %HOSTIP:%HTTPPORT --user iam:myself --proxy-user youare:yourself`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`CONNECT %HOSTIP:%HTTPPORT HTTP/1.0`
			`Host: %HOSTIP:%HTTPPORT`
General HTTP authentication cleanup and fixes 2004-05-04 03:52:53 -04:00			`Proxy-Authorization: Basic eW91YXJlOnlvdXJzZWxm`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04: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`
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`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04:00
			`GET /we/want/that/page/80 HTTP/1.1`
			`Authorization: Basic aWFtOm15c2VsZg==`
			`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-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
tunnel through proxy, with both proxy and regular authentication 2003-08-11 07:09:03 -04: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>`