aboutsummaryrefslogtreecommitdiff
path: root/tests/data/test2032
AgeCommit message (Collapse)Author
2019-12-31tests: Change NTLM tests to require SSLJay Satiro
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-06-25tests: update fixed IP for hostip/clientip splitStephan Szabo
These tests give differences for me on linux when using a hostip pointing to the external ip address for the local machine. Closes #4070
2019-01-01ntlm: update selection of type 3 responseMarkus Moeller
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
2017-08-13test2032: mark as flaky (again)Daniel Stenberg
2017-06-16tests: stabilize test 2032 and 2033Daniel Stenberg
Both these tests run the same underlying test code: libntlmconnect.c - this test code made some assumptions about socket ordering when it used curl_easy_fdset() and when we changed timing or got accidental changes in libcurl the tests would fail. The tests verify that the different transfers keep using the same connections, which I now instead made sure by adding the number of bytes each transfer gets and then verifies that they always get the same amount as when these tests worked. Closes #1576
2017-03-04tests: fixed a typo in some commentsDan Fandrich
2016-12-05test2032: Mark test as flakyDan Fandrich
2015-03-12test203[0-3]: Expect the Host header to be the first headerFabian Keil
Required for the tests to work after a5d994941c2b.
2014-02-14testsuite: changed HTTP and RTSP header line-endings to CRLFMarc Hoersken
According to RFC 2616 and RFC 2326 individual protocol elements, like headers and except the actual content, are terminated by using CRLF. Therefore the test data files for these protocols need to contain mixed line-endings if the actual protocol elements use CRLF while the file uses LF.
2013-12-28tests: Disabled NTLM tests when running with SSPI enabledSteve Holme
2013-08-15tests 2032, 2033: Don't hardcode port in expected outputTor Arntsen
2012-11-27dd missing NTLM feature for tests 2025, and 2028 to 2032Yang Tse
2012-08-31test2032: bail out after last transferDaniel Stenberg
The test would hang and get aborted with a "ABORTING TEST, since it seems that it would have run forever." until I prevented that from happening. I also fixed the data file which got broken CRLF line endings when I sucked down the path from Joe's repo == my fault. Removed #37 from KNOWN_BUGS as this fix and test case verifies exactly this.
2012-08-31NTLM: verify multiple connections workJoe Mason
Add test2032 to test that NTLM does not switch connections in the middle of the handshake