curl/tests/data/test177

<testcase>
# Server-side
<reply>
<data>
HTTP/1.1 302 *MOVED* swsclose swsbounce
Server: Microsoft-IIS/6.0
Location: /mooooo/177
Content-Type: text/html; charset=iso-8859-1

</data>
</reply>

# Client-side
<client>
# 
<server>
http
</server>
<features>
crypto
</features>
 <name>
HTTP POST --digest to server doing a 302-location response
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/177 -u auser:apasswd --digest -d "junkelijunk"
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
POST /177 HTTP/1.1
User-Agent: curl/7.12.1-CVS (i686-pc-linux-gnu) libcurl/7.12.1-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS libidn/0.4.6
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 0
Content-Type: application/x-www-form-urlencoded

</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 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 302 MOVED swsclose swsbounce`
			`Server: Microsoft-IIS/6.0`
			`Location: /mooooo/177`
			`Content-Type: text/html; charset=iso-8859-1`

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

			`# Client-side`
			`<client>`
			`#`
			`<server>`
			`http`
			`</server>`
Updated the test harness to add a new "crypto" feature check and updated the appropriate test case to use it. For now, this is treated the same as the "SSL" feature because curl doesn't list it separately. 2007-03-09 18:39:42 -05:00			`<features>`
			`crypto`
			`</features>`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00			`<name>`
			`HTTP POST --digest to server doing a 302-location response`
			`</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 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/177 -u auser:apasswd --digest -d "junkelijunk"`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
HTTP "auth done right". See lib/README.httpauth 2004-11-24 11:11:35 -05:00			`POST /177 HTTP/1.1`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00			`User-Agent: curl/7.12.1-CVS (i686-pc-linux-gnu) libcurl/7.12.1-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS libidn/0.4.6`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -04:00			`Accept: /`
HTTP "auth done right". See lib/README.httpauth 2004-11-24 11:11:35 -05:00			`Content-Length: 0`
			`Content-Type: application/x-www-form-urlencoded`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 06:10:50 -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>`