moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-10-31 23:55:01 -04:00
Code Issues Releases Wiki Activity
6dae798824
curl/tests/data/test175

87 lines
1.8 KiB
Plaintext
Raw Normal View History

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 some <keywords> sections and use some key words more consistently.
2007-10-11 21:44:22 -04:00
<info>
<keywords>
HTTP
HTTP POST
HTTP Digest auth
</keywords>
</info>
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
# Server-side
<reply>
<data>
HTTP/1.1 200 beng swsclose swsbounce
Server: Microsoft-IIS/6.0
Authentication-Info: Passport1.4 tname=MSPAuth,tname=MSPProf,tname=MSPConsent,tname=MSPSecAuth
Content-Type: text/html; charset=iso-8859-1
This is not the real page
</data>
<data1>
HTTP/1.1 200 moo swsclose
Server: Microsoft-IIS/6.0
Content-Type: text/html; charset=iso-8859-1
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
Content-Length: 16
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
content for you
</data1>
<datacheck>
HTTP/1.1 200 beng swsclose swsbounce
Server: Microsoft-IIS/6.0
Authentication-Info: Passport1.4 tname=MSPAuth,tname=MSPProf,tname=MSPConsent,tname=MSPSecAuth
Content-Type: text/html; charset=iso-8859-1
HTTP/1.1 200 moo swsclose
Server: Microsoft-IIS/6.0
Content-Type: text/html; charset=iso-8859-1
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2012-11-14 13:49:12 -05:00
Content-Length: 16
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
content for you
</datacheck>
</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>
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
<name>
HTTP POST --digest to server not requiring any auth at all
</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/175 -u auser:apasswd --digest -d "junkelijunk"
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-25 16:45:03 -05:00
</client>
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04: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. & => &amp; ). 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
<protocol nonewline="yes">
HTTP "auth done right". See lib/README.httpauth
2004-11-24 11:11:35 -05:00
POST /175 HTTP/1.1
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -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
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -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
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
POST /175 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
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
added test case 175, use HTTP POST and DIGEST set but the server requires no auth
2004-06-15 04:50:15 -04:00
Accept: */*
Content-Length: 11
Content-Type: application/x-www-form-urlencoded
junkelijunk
</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. & => &amp; ). 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>
Reference in New Issue Copy Permalink