curl/tests/data/test177

<testcase>
<info>
<keywords>
HTTP
HTTP POST
HTTP Digest auth
followlocation
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.1 302 *MOVED* swsclose swsbounce
Server: Microsoft-IIS/6.0
Location: /mooooo/%TESTNUMBER
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/%TESTNUMBER -u auser:apasswd --digest -d "junkelijunk"
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<protocol>
POST /%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
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-23 10:25:56 +08:00			`<testcase>`
Added some <keywords> sections and use some key words more consistently. 2007-10-12 09:44:22 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP POST`
			`HTTP Digest auth`
			`followlocation`
			`</keywords>`
			`</info>`

test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 302 MOVED swsclose swsbounce`
			`Server: Microsoft-IIS/6.0`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`Location: /mooooo/%TESTNUMBER`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00			`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-10 07:39:42 +08:00			`<features>`
			`crypto`
			`</features>`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00			`<name>`
			`HTTP POST --digest to server doing a 302-location response`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`http://%HOSTIP:%HTTPPORT/%TESTNUMBER -u auser:apasswd --digest -d "junkelijunk"`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-26 05:45:03 +08:00			`</client>`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`POST /%TESTNUMBER HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 19:45:24 +08:00			`User-Agent: curl/%VERSION`
test 177 HTTP POST with --digest that gets a 302 response 2004-06-19 18:10:50 +08:00			`Accept: /`
HTTP "auth done right". See lib/README.httpauth 2004-11-25 00:11:35 +08: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 18:10:50 +08: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-23 10:25:56 +08:00			`</testcase>`