delta/curl.git/tests/data/test548, branch bagder/test493-https

ntlm: fix negotiated flags usage

2021-04-09T07:40:56+00:00

According to Microsoft document MS-NLMP, current flags usage is not
accurate: flag NTLMFLAG_NEGOTIATE_NTLM2_KEY controls the use of
extended security in an NTLM authentication message and NTLM version 2
cannot be negotiated within the protocol.

The solution implemented here is: if the extended security flag is set,
prefer using NTLM version 2 (as a server featuring extended security
should also support version 2). If version 2 has been disabled at
compile time, use extended security.

Tests involving NTLM are adjusted to this new behavior.

Fixes #6813
Closes #6849

tests: use %TESTNUMBER instead of fixed number

2021-03-19T14:57:21+00:00

This makes the tests easier to copy and relocate to other test numbers
without having to update content.

Closes #6738

runtests: provide curl's version string as %VERSION for tests

2020-10-02T20:54:23+00:00

... so that we can check HTTP requests for User-Agent: curl/%VERSION

Update 600+ test cases accordingly.

Closes #6037

tests: Change NTLM tests to require SSL

2019-12-31T07:47:53+00:00

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 feature

2019-10-15T05:56:55+00:00

This makes the tests succeed when using --disable-proxy.

Closes https://github.com/curl/curl/pull/4488

ntlm: update selection of type 3 response

2019-01-01T10:47:17+00:00

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: updated for modified fake random

2017-05-08T21:24:43+00:00

Revert "Proxy-Connection: stop sending this header by default"

2016-08-16T06:36:04+00:00

This reverts commit 113f04e664b16b944e64498a73a4dab990fe9a68.

Proxy-Connection: stop sending this header by default

2016-02-08T10:09:40+00:00

RFC 7230 says we should stop. Firefox already stopped.

Bug: https://github.com/curl/curl/issues/633
Reported-By: Brad Fitzpatrick

Closes #633

http: always send Host: header as first header

2015-03-12T11:15:24+00:00

...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