moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-10 03:25:04 -05:00
Code Issues Releases Wiki Activity
da58d03ff7
curl/tests/data/test175

74 lines
1.6 KiB
Plaintext
Raw Normal View History

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
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: 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
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: 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>
<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>
<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
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
Host: 127.0.0.1:%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
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
Host: 127.0.0.1:%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>
Reference in New Issue Copy Permalink