summaryrefslogtreecommitdiff
path: root/tests/data/test1008
Commit message (Collapse)AuthorAgeFilesLines
* tests: Change NTLM tests to require SSLJay Satiro2019-12-311-0/+1
| | | | | | | | | | | | | | | | | | 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
* tests: use proxy featureMarcel Raad2019-10-151-0/+1
| | | | | | This makes the tests succeed when using --disable-proxy. Closes https://github.com/curl/curl/pull/4488
* ntlm: update selection of type 3 responseMarkus Moeller2019-01-011-3/+3
| | | | | | | | | | | 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
* tests: added missing keywords "chunked Transfer-Encoding"Dan Fandrich2017-05-131-0/+1
|
* tests: updated for modified fake randomDaniel Stenberg2017-05-081-1/+1
|
* Revert "Proxy-Connection: stop sending this header by default"Daniel Stenberg2016-08-161-0/+2
| | | | This reverts commit 113f04e664b16b944e64498a73a4dab990fe9a68.
* Proxy-Connection: stop sending this header by defaultDaniel Stenberg2016-02-081-2/+0
| | | | | | | | | RFC 7230 says we should stop. Firefox already stopped. Bug: https://github.com/curl/curl/issues/633 Reported-By: Brad Fitzpatrick Closes #633
* NTLM: set a fake entropy for debug builds with CURL_ENTROPY setDaniel Stenberg2014-06-111-1/+1
| | | | | | | | | | | | | | | | Curl_rand() will return a dummy and repatable random value for this case. Makes it possible to write test cases that verify output. Also, fake timestamp with CURL_FORCETIME set. Only when built debug enabled of course. Curl_ssl_random() was not used anymore so it has been removed. Curl_rand() is enough. create_digest_md5_message: generate base64 instead of hex string curl_sasl: also fix memory leaks in some OOM situations
* tests: Disabled NTLM tests for non-debug buildsSteve Holme2014-06-111-0/+1
| | | | | | 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.
* tests: Updated NTLM tests for NTLMv2 type-3 messageSteve Holme2014-01-301-2/+2
|
* tests: Disabled NTLM tests when running with SSPI enabledSteve Holme2013-12-281-0/+1
|
* test1509: verify proxy header response headers countDaniel Stenberg2013-03-271-10/+10
| | | | | | | | | | | | | Modified sws to support and use custom CONNECT responses instead of the previously naive hard-coded version. Made the HTTP test server able to extract test case number from the host name in a CONNECT request by finding the number after the last dot. It makes 'machine.moo.123' use test case 123. Adapted a larger amount of tests to the new <connect> style. Bug: http://curl.haxx.se/bug/view.cgi?id=1204 Reported by: Martin Jansen
* connection-monitor: always log disconnect when enabledDaniel Stenberg2012-07-121-0/+1
| | | | | | This makes verifying easier and makes us more sure curl closes the connection only at the correct point in time. Adjusted test 206 and 1008 accordingly and updated the docs for it.
* tests: use connection-monitor and verify resultsDaniel Stenberg2012-07-051-0/+3
| | | | | | Test 1008 and 206 don't show the disconnect since it happens when SWS awaits a new request, but 503 does and so the verify section needs that string added.
* tests: phase out haxx.seDaniel Stenberg2011-03-091-6/+6
| | | | | | Instead of using haxx.se as a fixed magic host name in lots of tests, this is a first step to move toward the generic example.com host instead.
* Make the LD_PRELOAD path absolute in the tests that use itDan Fandrich2010-08-161-1/+1
| | | | | | | | 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.
* NTLM tests: boost coverage by forcing the hostnameKamil Dudka2010-07-301-6/+10
| | | | | | | | | | | | | 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.
* Changed host name to be under the haxx.se domainYang Tse2009-05-081-6/+6
|
* - Craig A West brought us: libcurl now defaults to do CONNECT with HTTPDaniel Stenberg2009-02-021-2/+2
| | | | | | | | | | version 1.1 instead of 1.0 like before. This change also introduces the new proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0 option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0. I updated all test cases cases that use CONNECT and I tried to do some using --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run.
* Added HTTP CONNECT keywordsDan Fandrich2008-08-111-1/+2
|
* add keywordsDaniel Stenberg2007-12-081-0/+9
|
* known bug #46: chunked-encoded CONNECT responses from a http proxy now works.Daniel Stenberg2007-10-021-0/+112
Added test case 1008 to verify. Note that #47 is still there.
View Lorry Controller Status