d5dc3629 | 20-Jun-2022 |
Daniel Stenberg |
easy: remove dead code Follow-up from 5912da253b64d Detected by Coverity (CID 1506519) Closes #9029 |
7f43f3dc | 06-Jun-2022 |
Glenn Strauss |
transfer: upload performance; avoid tiny send Append to the upload buffer when only small amount remains in buffer rather than performing a separate tiny send to empty buffer. A
transfer: upload performance; avoid tiny send Append to the upload buffer when only small amount remains in buffer rather than performing a separate tiny send to empty buffer. Avoid degenerative upload behavior which might cause curl to send mostly 1-byte DATA frames after exhausing the h2 send window size Related discussion: https://github.com/nghttp2/nghttp2/issues/1722 Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com> Closes #8965
show more ...
|
aea8ac14 | 09-Jun-2022 |
Steve Holme |
projects: fix third-party SSL library build paths for Visual Studio The paths used by the build batch files were inconsistent with those in the Visual Studio project files. Clos
projects: fix third-party SSL library build paths for Visual Studio The paths used by the build batch files were inconsistent with those in the Visual Studio project files. Closes #8991
show more ...
|
4bf2c231 | 19-Jun-2022 |
Pierrick Charron |
urlapi: make curl_url_set(url, CURLUPART_URL, NULL, 0) clear all parts As per the documentation : > Setting a part to a NULL pointer will effectively remove that > part's conten
urlapi: make curl_url_set(url, CURLUPART_URL, NULL, 0) clear all parts As per the documentation : > Setting a part to a NULL pointer will effectively remove that > part's contents from the CURLU handle. But currently clearing CURLUPART_URL does nothing and returns CURLUE_OK. This change will clear all parts of the URL at once. Closes #9028
show more ...
|
06fc9583 | 26-May-2022 |
Philip H <47042125+pheiduck@users.noreply.github.com> |
CI: bump FreeBSD 13.0 to 13.1 Signed-off-by: Philip H <47042125+pheiduck@users.noreply.github.com> Closes #8815 |
dd7864da | 18-Jun-2022 |
Daniel Stenberg |
RELEASE-NOTES: synced and updated release date in RELEASE-PROCEDURE.md |
8dcbb0f1 | 17-Jun-2022 |
divinity76 |
CURLOPT_HTTPHEADER.3: improve comment in example Closes #9025 |
3084f877 | 14-Jun-2022 |
Marc Hoersken |
CI/azure: reduce flakiness by retrying install/prepare steps Closes #9010 |
0263c828 | 14-Jun-2022 |
Marc Hoersken |
CI/cirrus: align Windows timeout with Azure CI at 120 minutes Closes #9009 |
a8a4abb2 | 15-Jun-2022 |
Jay Satiro |
vtls: make curl_global_sslset thread-safe .. and update some docs to explain curl_global_* is now thread-safe. Follow-up to 23af112 which made curl_global_init/cleanup thread-safe.
vtls: make curl_global_sslset thread-safe .. and update some docs to explain curl_global_* is now thread-safe. Follow-up to 23af112 which made curl_global_init/cleanup thread-safe. Closes https://github.com/curl/curl/pull/9016
show more ...
|
9135275f | 15-Jun-2022 |
Jay Satiro |
curl_easy_pause.3: remove explanation of progress function - Remove misleading text that says progress function "gets called at least once per second, even if the connection is paused.
curl_easy_pause.3: remove explanation of progress function - Remove misleading text that says progress function "gets called at least once per second, even if the connection is paused." The progress function behavior is more nuanced and the user is better served reading the progress function doc rather than attempt to explain it in the curl_easy_pause doc. The progress function can only be called at least once per second if an appropriate multi transfer function is called (eg curl_multi_perform) in that time. For a paused transfer there may not be such a call. Rather than explain this in detail in the curl_easy_pause doc, rely on the user reading the CURLOPT_PROGRESSFUNCTION doc. Ref: https://github.com/curl/curl/issues/8983 Closes https://github.com/curl/curl/pull/9015
show more ...
|
ef22d5c4 | 15-Jun-2022 |
Daniel Stenberg |
libssh: skip the fake-close when libssh does the right thing Starting in libssh 0.10.0 ssh_disconnect() will no longer close our socket. Instead it will be kept alive as we want it, and
libssh: skip the fake-close when libssh does the right thing Starting in libssh 0.10.0 ssh_disconnect() will no longer close our socket. Instead it will be kept alive as we want it, and it is our responsibility to close it later. Ref: #8718 Ref: https://gitlab.com/libssh/libssh-mirror/-/merge_requests/240 Closes #9021
show more ...
|
c828dc72 | 15-Jun-2022 |
Daniel Stenberg |
configure: warn about rustls being experimental Right now a dozen test cases are disabled because they don't work with rustls. Closes #9019 |
f0f587d3 | 14-Jun-2022 |
Daniel Stenberg |
runtests: skip starting the ssh server if user name is lacking Because the ssh server startup script *requires* a user name there's no point in invoking it if no name was found.
runtests: skip starting the ssh server if user name is lacking Because the ssh server startup script *requires* a user name there's no point in invoking it if no name was found. Reported-by: Ricardo M. Correia Ref: #9007 Closes #9013
show more ...
|
4572489c | 14-Jun-2022 |
Daniel Stenberg |
copyright.pl: parse and use .reuse/dep5 for skips Also scan skipped files to be able to find superfluous ignores, shown with -v. Closes #9006 |
2b7f7d04 | 14-Jun-2022 |
Daniel Stenberg |
reuse/dep5: adjusted to parse better ... adjusted a few files to contain copyright and license info. Closes #9006 |
10f8fe36 | 14-Jun-2022 |
Daniel Stenberg |
buildconf.bat: update copyright year range Closes #9006 |
6c616ba1 | 14-Jun-2022 |
Daniel Stenberg |
README.md: use the common "Copyright" style formatting Closes #9006 |
c2ad703e | 14-Jun-2022 |
Daniel Stenberg |
reuse: move license info from .mailmap.license to .reuse/dep5 Closes #9006 |
20e05073 | 14-Jun-2022 |
Daniel Stenberg |
README.md: add a REUSE badge Closes #9004 |
a33f90b1 | 14-Jun-2022 |
Daniel Stenberg |
.reuse/dep5: remove recursive docs ignore, only skip markdown files ... and some additional non-markdown individual files in docs/ Closes #9005 |
df45fd17 | 13-Jun-2022 |
Daniel Stenberg |
docs/cmdline-opts: add copyright and license identifier to each file gen.pl now insists on C: and SPDX-License-Identifier: fields to be present in all files. Closes #9002 |
d82c7eed | 13-Jun-2022 |
Daniel Stenberg |
copyright: info for/ignore .github/ISSUE_TEMPLATE/bug_report.md Follow-up from 448f7ef9ab2afb7. The adding of the copyright text in that file broke site functionality. Closes #9
copyright: info for/ignore .github/ISSUE_TEMPLATE/bug_report.md Follow-up from 448f7ef9ab2afb7. The adding of the copyright text in that file broke site functionality. Closes #9001
show more ...
|
448f7ef9 | 13-Jun-2022 |
Daniel Stenberg |
bug_report.md: revert the REUSE template to see if it works again |
a94d6fe7 | 13-Jun-2022 |
Viktor Szakats |
version: rename threadsafe-init to threadsafe Referring to Daniel's article [1], making the init function thread-safe was the last bit to make libcurl thread-safe as a whole. So the name
version: rename threadsafe-init to threadsafe Referring to Daniel's article [1], making the init function thread-safe was the last bit to make libcurl thread-safe as a whole. So the name of the feature may as well be the more concise 'threadsafe', also telling the story that libcurl is now fully thread-safe, not just its init function. Chances are high that libcurl wants to remain so in the future, so there is little likelihood of ever needing any other distinct `threadsafe-<name>` feature flags. For consistency we also shorten `CURL_VERSION_THREADSAFE_INIT` to `CURL_VERSION_THREADSAFE`, update its description and reference libcurl's thread safety documentation. [1]: https://daniel.haxx.se/blog/2022/06/08/making-libcurl-init-more-thread-safe/ Reviewed-by: Daniel Stenberg Reviewed-by: Jay Satiro Closes #8989
show more ...
|