curl - cURL mirror with patches applied

Age	Commit message (Collapse)	Author
2015-03-12	http: always send Host: header as first header	Daniel Stenberg
	...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
2014-11-06	tests: Don't run HTTP digest tests for SSPI based builds	Steve Holme
	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.
2012-11-19	Do not mix CRLF and LF header endings in a couple of HTTP tests	Fabian Keil
	Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this.
2007-09-14	Replaced 127.0.0.1 with %HOSTIP where possible	Dan Fandrich

2007-03-09	Updated the test harness to add a new "crypto" feature check and updated the	Dan Fandrich
	appropriate test case to use it. For now, this is treated the same as the "SSL" feature because curl doesn't list it separately.
2007-01-23	Convert (most of) the test data files into genuine XML. A handful still	Dan Fandrich
	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.
2006-11-25	Venkat Akella found out that libcurl did not like HTTP responses that simply	Daniel Stenberg
	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.
2005-10-20	Dave Dribin made libcurl understand and handle cases when the server	Daniel Stenberg
	(wrongly) sends two WWW-Authenticate headers for Digest. While this should never happen in a sane world, libcurl previously got into an infinite loop when this occurred. Dave added test 273 to verify this.