Unity-Technologies
/
curl
зеркало из https://github.com/Unity-Technologies/curl.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
curl/tests/data/test89

149 строки
4.6 KiB
Plaintext
Исходник Обычный вид История

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 05:25:56 +03:00
<testcase>
keyword update
2005-04-27 13:59:47 +04:00
<info>
<keywords>
HTTP
HTTP GET
HTTP NTLM auth
followlocation
</keywords>
</info>
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
# Server-side
<reply>
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 05:25:56 +03:00
<!-- no <data> in this test since we have NTLM from the start
This is supposed to be returned when the server gets a first
Authorization: NTLM line passed-in from the client -->
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
<data1001>
HTTP/1.1 401 Now gimme that second request of crap
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
Content-Length: 34
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
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>
HTTP/1.1 301 Things are fine in server land swsclose
Server: Microsoft-IIS/5.0
Connection: close
Location: /you/890010
</data1002>
# This is the first reply after the redirection
<data1011>
HTTP/1.1 401 Now gimme that second round of crap
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
Content-Length: 34
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
This is not the real page either!
</data1011>
# This is supposed to be returned when the server gets the second
# Authorization: NTLM line passed-in from the client
<data1012>
HTTP/1.1 200 Things are fine in server land swsclose
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 16:32:04 +03:00
Content-Length: 32
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
Finally, this is the real page!
</data1012>
<datacheck>
HTTP/1.1 401 Now gimme that second request of crap
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
Content-Length: 34
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
HTTP/1.1 301 Things are fine in server land swsclose
Server: Microsoft-IIS/5.0
Connection: close
Location: /you/890010
HTTP/1.1 401 Now gimme that second round of crap
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
Content-Length: 34
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAACGggEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
HTTP/1.1 200 Things are fine in server land swsclose
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 16:32:04 +03:00
Content-Length: 32
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04: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 11:14:32 +03:00
NTLM
tests: Change NTLM tests to require SSL Prior to this change tests that required NTLM feature did not require SSL feature. There are pending changes to cmake builds that will allow enabling NTLM in non-SSL builds in Windows. In that case the NTLM auth strings created are different from what is expected by the NTLM tests and they fail: "The issue with NTLM is that previous non-SSL builds would not enable NTLM and so the NTLM tests would be skipped." Assisted-by: marc-groundctl@users.noreply.github.com Ref: https://github.com/curl/curl/pull/4717#issuecomment-566218729 Closes https://github.com/curl/curl/pull/4768
2019-12-29 23:23:25 +03:00
SSL
tests: Disabled NTLM tests when running with SSPI enabled
2013-12-29 00:22:22 +04:00
!SSPI
tests: Disabled NTLM tests for non-debug builds Added required "debug" feature, missed in commit 1c9aaa0bac, as NTLMv2 calls Curl_rand() which can only be fixed to a specific entropy in debug builds.
2014-06-11 21:12:48 +04:00
debug
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
</features>
<server>
http
</server>
<name>
HTTP with NTLM and follow-location
</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 02:47:49 +04: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 00:36:04 +04: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 02:47:49 +04:00
</setenv>
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04: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 12:08:38 +04:00
http://%HOSTIP:%HTTPPORT/89 -u testuser:testpass --ntlm -L
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04: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 02:47:49 +04:00
<precheck>
chkhostname curlhost
</precheck>
A minor "syntax error" in numerous test files corrected
2005-01-26 00:45:03 +03:00
</client>
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /89 HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-12 02:50:46 +03:00
Host: %HOSTIP:%HTTPPORT
NTLM2 session response support
2006-06-07 18:14:04 +04:00
Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04: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
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 15:46:41 +03:00
Accept: */*
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
GET /89 HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-12 02:50:46 +03:00
Host: %HOSTIP:%HTTPPORT
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADQzMjE1MzIxAAAAAAAAAAAAAAAAAAAAADj3hs3u3j0kgJqCrLM+74BmaoNHDfIJjHRlc3R1c2VyY3VybGhvc3Q=
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04: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
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 15:46:41 +03:00
Accept: */*
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
GET /you/890010 HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-12 02:50:46 +03:00
Host: %HOSTIP:%HTTPPORT
NTLM2 session response support
2006-06-07 18:14:04 +04:00
Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
User-Agent: curl/7.10.8-pre1 (i686-pc-linux-gnu) libcurl/7.10.8-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3 GSS
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 15:46:41 +03:00
Accept: */*
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
GET /you/890010 HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-12 02:50:46 +03:00
Host: %HOSTIP:%HTTPPORT
ntlm: update selection of type 3 response NTLM2 did not work i.e. no NTLMv2 response was created. Changing the check seems to work. Ref: https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-NLMP/[MS-NLMP].pdf Fixes https://github.com/curl/curl/issues/3286 Closes https://github.com/curl/curl/pull/3287 Closes https://github.com/curl/curl/pull/3415
2018-12-28 17:04:53 +03:00
Authorization: NTLM TlRMTVNTUAADAAAAGAAYAEAAAAAYABgAWAAAAAAAAABwAAAACAAIAHAAAAAIAAgAeAAAAAAAAAAAAAAAhoIBADYzMjE3MzIxAAAAAAAAAAAAAAAAAAAAAEcJ4YHOeb5ga2TCPwDhkyUIuHjBUHcLaHRlc3R1c2VyY3VybGhvc3Q=
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +04:00
User-Agent: curl/7.10.8-pre1 (i686-pc-linux-gnu) libcurl/7.10.8-pre1 OpenSSL/0.9.7a ipv6 zlib/1.1.3 GSS
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 15:46:41 +03:00
Accept: */*
test 89 verifies -L and ntlm authentication, as bug report #806328 claimed it doesn't work. It works for me.
2003-09-16 01:41:45 +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. & => &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 05:25:56 +03:00
</testcase>