curl/tests/data/test301

<testcase>
<info>
<keywords>
HTTPS
HTTP GET
HTTP Basic auth
</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
Content-Type: text/html
Funny-head: yesyes

</data>
</reply>

#
# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
 <name>
HTTPS GET with user and password
 </name>
 <command>
-k -u fake:user https://%HOSTIP:%HTTPSPORT/301
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /301 HTTP/1.1
Authorization: Basic ZmFrZTp1c2Vy
Host: %HOSTIP:%HTTPSPORT
Accept: */*

</protocol>
<data>
[insert full protocol verifiction dump here]
</data>
</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 key words to all SSL-using tests so they can be skipped if necessary. Removed a few unnecessary requires SSL statements. 2008-02-08 21:08:34 -05:00			`<info>`
			`<keywords>`
			`HTTPS`
			`HTTP GET`
			`HTTP Basic auth`
			`</keywords>`
			`</info>`

HTTPS test case 2001-09-18 11:13:40 -04: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`
HTTPS test case 2001-09-18 11:13:40 -04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`
			`Content-Type: text/html`
			`Funny-head: yesyes`

			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
properly mark tests as requiring feature 'SSL' 2005-01-30 07:53:05 -05:00			`<features>`
			`SSL`
			`</features>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`https`
			`</server>`
HTTPS test case 2001-09-18 11:13:40 -04:00			`<name>`
			`HTTPS GET with user and password`
			`</name>`
			`<command>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`-k -u fake:user https://%HOSTIP:%HTTPSPORT/301`
HTTPS test case 2001-09-18 11:13:40 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
HTTPS test case 2001-09-18 11:13:40 -04:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`GET /301 HTTP/1.1`
HTTPS test case 2001-09-18 11:13:40 -04:00			`Authorization: Basic ZmFrZTp1c2Vy`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPSPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
HTTPS test case 2001-09-18 11:13:40 -04:00
			`</protocol>`
			`<data>`
			`[insert full protocol verifiction dump here]`
			`</data>`
			`</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>`