curl/tests/data/test153, branch master

digest: Do not quote algorithm in HTTP authorisation

2020-02-07T21:46:21+00:00

RFC 7616 section 3.4 (The Authorization Header Field) states that "For
historical reasons, a sender MUST NOT generate the quoted string syntax
for the following parameters: algorithm, qop, and nc". This removes the
quoting for the algorithm parameter.

Reviewed-by: Steve Holme
Closes #4890

curl: support parallel transfers

2019-07-20T17:14:16+00:00

This is done by making sure each individual transfer is first added to a
linked list as then they can be performed serially, or at will, in
parallel.

Closes #3804

test153: fix content-length to avoid occasional hang

2019-06-24T06:33:32+00:00

Closes #4065

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

tests: Don't run HTTP digest tests for SSPI based builds

2014-11-06T20:36:08+00:00

Added !SSPI to the features list of the HTTP digest tests, as SSPI
based builds now use the Windows SSPI messaging API rather than the
internal functions, and we can't control the random numbers that get
used as part of the digest.

Added some sections and use some key words more consistently.

2007-10-12T01:44:22+00:00

Replaced 127.0.0.1 with %HOSTIP where possible

2007-09-14T19:32:31+00:00

Updated the test harness to add a new "crypto" feature check and updated the

2007-03-09T23:39:42+00:00

appropriate test case to use it.  For now, this is treated the same as the
"SSL" feature because curl doesn't list it separately.

Convert (most of) the test data files into genuine XML. A handful still

2007-01-23T02:25:56+00:00

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.

Venkat Akella found out that libcurl did not like HTTP responses that simply

2006-11-25T13:32:04+00:00

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.