mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-27 06:59:43 +08:00
Code Issues Packages Projects Releases Wiki Activity
8896b56488
curl/tests/data/test69

122 lines
3.4 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-23 10:25:56 +08:00
<testcase>
keywords added
2005-04-23 05:59:08 +08:00
<info>
<keywords>
HTTP
HTTP GET
HTTP NTLM auth
</keywords>
</info>
new tests
2003-06-26 19:45:04 +08:00
# Server-side
<reply>
<data>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
HTTP/1.1 401 Authorization Required swsclose
new tests
2003-06-26 19:45:04 +08:00
Server: Apache/1.3.27 (Darwin) PHP/4.1.2
WWW-Authenticate: Basic
WWW-Authenticate: Wild-and-crazy
WWW-Authenticate: NTLM
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 21:32:04 +08:00
Content-Length: 26
new tests
2003-06-26 19:45:04 +08:00
This is not the real page
</data>
# This is supposed to be returned when the server gets a first
# Authorization: NTLM line passed-in from the client
<data1001>
HTTP/1.1 401 Now gimme that second request of crap
Server: Microsoft-IIS/5.0
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
Content-Length: 34
new tests
2003-06-26 19:45:04 +08:00
Content-Type: text/html; charset=iso-8859-1
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
This is not the real page either!
</data1001>
# This is supposed to be returned when the server gets the second
# Authorization: NTLM line passed-in from the client
<data1002>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
HTTP/1.1 200 Things are fine in server land swsclose
new tests
2003-06-26 19:45:04 +08:00
Server: Microsoft-IIS/5.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 21:32:04 +08:00
Content-Length: 32
new tests
2003-06-26 19:45:04 +08:00
Finally, this is the real page!
</data1002>
<datacheck>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
HTTP/1.1 401 Authorization Required swsclose
new tests
2003-06-26 19:45:04 +08:00
Server: Apache/1.3.27 (Darwin) PHP/4.1.2
WWW-Authenticate: Basic
WWW-Authenticate: Wild-and-crazy
WWW-Authenticate: NTLM
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 21:32:04 +08:00
Content-Length: 26
new tests
2003-06-26 19:45:04 +08:00
HTTP/1.1 401 Now gimme that second request of crap
Server: Microsoft-IIS/5.0
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
Content-Length: 34
new tests
2003-06-26 19:45:04 +08:00
Content-Type: text/html; charset=iso-8859-1
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
HTTP/1.1 200 Things are fine in server land swsclose
new tests
2003-06-26 19:45:04 +08:00
Server: Microsoft-IIS/5.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 21:32:04 +08:00
Content-Length: 32
new tests
2003-06-26 19:45:04 +08:00
Finally, this is the real page!
</datacheck>
</reply>
# Client-side
<client>
<features>
Make NTLM tests depend on the NTLM feature at not SSL, since the NTLM support is no longer only present when built with SSL support.
2005-03-21 16:14:32 +08:00
NTLM
new tests
2003-06-26 19:45:04 +08:00
</features>
<server>
http
</server>
<name>
HTTP with NTLM, Basic or Wild-and-crazy authorization
</name>
NTLM tests: boost coverage by forcing the hostname A shared library tests/libtest/.libs/lihostname.so is preloaded in NTLM test-cases to override the system implementation of gethostname(). It makes it possible to test the NTLM authentication for exact match, and this way test the implementation of MD4 and DES. If LD_PRELOAD doesn't work, a debug build willl also workk as debug builds are now made to prefer a specific environment variable and will then return that content as host name instead of the actual one. Kamil wrote the bulk of this, Daniel Stenberg polished it.
2010-07-30 06:47:49 +08:00
<setenv>
# we force our own host name, in order to make the test machine independent
CURL_GETHOSTNAME=curlhost
# we try to use the LD_PRELOAD hack, if not a debug build
Make the LD_PRELOAD path absolute in the tests that use it In some situations, libtool will change directories and perform a link step before executing the libtest test app. Since LD_PRELOAD is in effect for this entire process, the path to the binary must be absolute so it will be valid no matter in which directory the app is running.
2010-08-17 04:36:04 +08:00
LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
NTLM tests: boost coverage by forcing the hostname A shared library tests/libtest/.libs/lihostname.so is preloaded in NTLM test-cases to override the system implementation of gethostname(). It makes it possible to test the NTLM authentication for exact match, and this way test the implementation of MD4 and DES. If LD_PRELOAD doesn't work, a debug build willl also workk as debug builds are now made to prefer a specific environment variable and will then return that content as host name instead of the actual one. Kamil wrote the bulk of this, Daniel Stenberg polished it.
2010-07-30 06:47:49 +08:00
</setenv>
new tests
2003-06-26 19:45:04 +08:00
<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 16:08:38 +08:00
http://%HOSTIP:%HTTPPORT/69 -u testuser:testpass --anyauth
new tests
2003-06-26 19:45:04 +08:00
</command>
NTLM tests: boost coverage by forcing the hostname A shared library tests/libtest/.libs/lihostname.so is preloaded in NTLM test-cases to override the system implementation of gethostname(). It makes it possible to test the NTLM authentication for exact match, and this way test the implementation of MD4 and DES. If LD_PRELOAD doesn't work, a debug build willl also workk as debug builds are now made to prefer a specific environment variable and will then return that content as host name instead of the actual one. Kamil wrote the bulk of this, Daniel Stenberg polished it.
2010-07-30 06:47:49 +08:00
<precheck>
chkhostname curlhost
</precheck>
A minor "syntax error" in numerous test files corrected
2005-01-26 05:45:03 +08:00
</client>
new tests
2003-06-26 19:45:04 +08:00
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /69 HTTP/1.1
User-Agent: curl/7.10.6-pre1 (i686-pc-linux-gnu) libcurl/7.10.6-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-15 03:32:31 +08:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 20:46:41 +08:00
Accept: */*
new tests
2003-06-26 19:45:04 +08:00
GET /69 HTTP/1.1
NTLM2 session response support
2006-06-07 22:14:04 +08:00
Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
new tests
2003-06-26 19:45:04 +08:00
User-Agent: curl/7.10.6-pre1 (i686-pc-linux-gnu) libcurl/7.10.6-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-15 03:32:31 +08:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 20:46:41 +08:00
Accept: */*
new tests
2003-06-26 19:45:04 +08:00
GET /69 HTTP/1.1
NTLM tests: boost coverage by forcing the hostname A shared library tests/libtest/.libs/lihostname.so is preloaded in NTLM test-cases to override the system implementation of gethostname(). It makes it possible to test the NTLM authentication for exact match, and this way test the implementation of MD4 and DES. If LD_PRELOAD doesn't work, a debug build willl also workk as debug builds are now made to prefer a specific environment variable and will then return that content as host name instead of the actual one. Kamil wrote the bulk of this, Daniel Stenberg polished it.
2010-07-30 06:47:49 +08:00
Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAABoKBAFpkQwKRCZFMhjj0tw47wEjKHRHlvzfxQamFcheMuv8v+xeqphEO5V41xRd7R9deOXRlc3R1c2VyY3VybGhvc3Q=
new tests
2003-06-26 19:45:04 +08:00
User-Agent: curl/7.10.6-pre1 (i686-pc-linux-gnu) libcurl/7.10.6-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-15 03:32:31 +08:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 20:46:41 +08:00
Accept: */*
new tests
2003-06-26 19:45:04 +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. & => &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-23 10:25:56 +08:00
</testcase>
Reference in New Issue Copy Permalink