<feed xmlns='http://www.w3.org/2005/Atom'>
<title>curl/tests/data/test1418, branch master</title>
<subtitle>cURL mirror with patches applied
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/'/>
<entry>
<title>curl: support parallel transfers</title>
<updated>2019-07-20T17:14:16+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2019-07-20T17:14:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=b88940850002a3f1c25bc6488b95ad30eb80d696'/>
<id>b88940850002a3f1c25bc6488b95ad30eb80d696</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>http: always send Host: header as first header</title>
<updated>2015-03-12T11:15:24+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2015-03-11T23:50:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=a5d994941c2b19a3c63402caa064c9683647de05'/>
<id>a5d994941c2b19a3c63402caa064c9683647de05</id>
<content type='text'>
...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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
...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
</pre>
</div>
</content>
</entry>
<entry>
<title>tests: Don't run HTTP digest tests for SSPI based builds</title>
<updated>2014-11-06T20:36:08+00:00</updated>
<author>
<name>Steve Holme</name>
<email>steve_holme@hotmail.com</email>
</author>
<published>2014-11-06T19:57:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=b5c496f1090ab8a8c535acde33af61f197bd99ba'/>
<id>b5c496f1090ab8a8c535acde33af61f197bd99ba</id>
<content type='text'>
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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>ConnectionExists: re-use connections better</title>
<updated>2014-02-16T13:30:02+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2014-02-16T13:07:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=d765099813f58153cb859279c743e6494d179341'/>
<id>d765099813f58153cb859279c743e6494d179341</id>
<content type='text'>
When allowing NTLM, the re-use connection logic was too focused on
finding an existing NTLM connection to use and didn't properly allow
re-use of other ones. This made the logic not re-use perfectly re-usable
connections.

Added test case 1418 and 1419 to verify.

Regression brought in 8ae35102c (curl 7.35.0)

Reported-by: Jeff King
Bug: http://thread.gmane.org/gmane.comp.version-control.git/242213
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When allowing NTLM, the re-use connection logic was too focused on
finding an existing NTLM connection to use and didn't properly allow
re-use of other ones. This made the logic not re-use perfectly re-usable
connections.

Added test case 1418 and 1419 to verify.

Regression brought in 8ae35102c (curl 7.35.0)

Reported-by: Jeff King
Bug: http://thread.gmane.org/gmane.comp.version-control.git/242213
</pre>
</div>
</content>
</entry>
</feed>
