curl/tests/data/test1030, branch master cURL mirror with patches applied http: always send Host: header as first header 2015-03-12T11:15:24+00:00 Daniel Stenberg daniel@haxx.se 2015-03-11T23:50:46+00:00 a5d994941c2b19a3c63402caa064c9683647de05 ...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 
...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 Steve Holme steve_holme@hotmail.com 2014-11-06T19:57:16+00:00 b5c496f1090ab8a8c535acde33af61f197bd99ba 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 !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.
- Ben Van Hof filed bug report #1945240: "libcurl sometimes sends body twice 2008-05-03T21:45:12+00:00 Daniel Stenberg daniel@haxx.se 2008-05-03T21:45:12+00:00 fc9e0d2249c126ccc8688c19bdf64c782778d6ab when using CURL_AUTH_ANY" (http://curl.haxx.se/bug/view.cgi?id=1945240). The problem was that when libcurl rewound a stream meant for upload when it would prepare for a second request, it could accidentally continue the sending of the rewound data on the first request instead of on the second. Ben also provided test case 1030 that verifies this fix. 
  when using CURL_AUTH_ANY" (http://curl.haxx.se/bug/view.cgi?id=1945240).
  The problem was that when libcurl rewound a stream meant for upload when it
  would prepare for a second request, it could accidentally continue the
  sending of the rewound data on the first request instead of on the second.
  Ben also provided test case 1030 that verifies this fix.