| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Signed-off-by: Dan Kenigsberg <danken@redhat.com>
Closes #5876
|
|
|
|
|
|
|
|
| |
As reported by man(1) when invoked as:
man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null
Closes #5846
|
|
|
|
| |
Closes #5846
|
|
|
|
| |
Follow-up to 6ebe63fac23f38
|
|
|
|
|
|
| |
To allow disabling of the curl_easy_option APIs in a build.
Closes #5365
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
const struct curl_easyoption *curl_easy_option_by_name(const char *name);
const struct curl_easyoption *curl_easy_option_by_id (CURLoption id);
const struct curl_easyoption *
curl_easy_option_next(const struct curl_easyoption *prev);
The purpose is to provide detailed enough information to allow for
example libcurl bindings to get option information at run-time about
what easy options that exist and what arguments they expect.
Assisted-by: Jeroen Ooms
Closes #5365
|
|
|
|
| |
Closes #5871
|
|
|
|
|
|
| |
... to completely disable the use of socketpair
Closes #5850
|
|
|
|
| |
Follow-up to 5620d2cc78c0
|
|
|
|
|
|
|
|
| |
Works with --create-dirs and with -J
Add test 3008, 3009, 3011, 3012 and 3013 to verify.
Closes #5637
|
|
|
|
|
|
| |
Replace the old fingerprint of the host with a new.
Closes #5685
|
|
|
|
|
|
|
|
|
| |
Added test433 to verify. Updated documentation.
Reviewed-by: Jay Satiro
Suggested-by: Eli Schwartz
Fixes #5829
Closes #5837
|
|
|
|
| |
Closes #5810
|
|
|
|
|
|
|
|
|
|
|
|
| |
Failures clearly returned from a (SOCKS) proxy now causes this return
code. Previously the situation was not very clear as what would be
returned and when.
In addition: when this error code is returned, an application can use
CURLINFO_PROXY_ERROR to query libcurl for the detailed error, which then
returns a value from the new 'CURLproxycode' enum.
Closes #5770
|
|
|
|
|
|
|
|
|
| |
Also: the current behavior is now documented in the curl.1 and
CURLOPT_NOPROXY.3 man pages.
Reported-by: Andrew Barnes
Closes #5745
Closes #5841
|
|
|
|
|
|
|
|
|
|
| |
Similarly to brotli, where this was already possible.
E.g. it allows to link zstd statically to libcurl.dll.
Ref: https://github.com/curl/curl-for-win/issues/12
Ref: https://github.com/curl/curl-for-win/commit/d9b266afd2e5d3f5604483010ef62340b5918c89
Closes https://github.com/curl/curl/pull/5840
|
|
|
|
| |
Closes #5835
|
| |
|
|
|
|
|
|
| |
Reported-by: plujon@users.noreply.github.com
Closes https://github.com/curl/curl/issues/5488
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
According to wikipedia:
While "web site" was the original spelling, this variant has become
rarely used, and "website" has become the standard spelling
Closes #5822
|
|
|
|
|
|
|
|
|
| |
... in particular what happens if the maximum speed limit is set to a
value that's smaller than the transfer buffer size in use.
Reported-by: Tomas Berger
Fixes #5788
Closes #5813
|
|
|
|
| |
Closes #5811
|
| |
|
|
|
|
|
| |
Closes #4915
Closes #5802
|
|
|
|
|
|
| |
In particular how the first line works.
Closes #5803
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The CMake option is now called CMAKE_USE_SCHANNEL
The winbuild flag is USE_SCHANNEL
The CI jobs and build scripts only use the new names and the new name
options
Tests now require 'Schannel' (when necessary)
Closes #5795
|
|
|
|
|
|
| |
93 - 96 can be returned as well.
Closes #5777
|
|
|
|
| |
Closes #5774
|
|
|
|
| |
Closes #5768
|
|
|
|
|
|
| |
... and rephrase that "not all" TLS backends support it.
Closes #5764
|
|
|
|
|
| |
Ref: #5763
Closes #5764
|
|
|
|
|
|
|
|
|
|
| |
Without the -D command line option, checksrc.pl won't know which
directory to load the ".checksrc" file from when building out of the
source tree.
Reported-by: Marcel Raad
Fixes #5715
Closes #5755
|
|
|
|
|
|
|
|
|
| |
We should offer an option to allow abrupt server closures (server closes
SSL transfer without sending a known termination point such as length of
transfer or close_notify alert). Abrupt server closures are usually
because of misconfigured or very old servers.
Closes https://github.com/curl/curl/issues/4427
|
|
|
|
|
|
|
|
| |
it helps make it obvious that most developers don't have to care about
the CURLM_CALL_MULTI_PERFORM value (last release using it is nearly 11
years old, November 4 2009)
Closes #5744
|
|
|
|
|
|
|
|
|
| |
They're not thread-safe so they should not be used in libcurl code.
Explictly enabled when deemed necessary and in examples and tests
Reviewed-by: Nicolas Sterchele
Closes #5732
|
|
|
|
|
|
| |
As test 1140 fails otherwise!
Follow-up to e1bac81cc815
|
|
|
|
|
|
|
| |
... and mention that HTTP with other methods than HEAD might get a body and
there's no option available to stop that.
Closes #5729
|
|
|
|
|
|
|
|
|
|
| |
This is required after https://github.com/cloudflare/quiche/pull/593
moved BoringSSL around slightly.
This also means that Go is not needed to build BoringSSL anymore (the
one provided by quiche anyway).
Closes #5691
|
|
|
|
|
|
|
|
|
| |
Add protocol and version specific information about all protocols curl
supports.
Fixes #5679
Reported-by: tbugfinder on github
Closes #5686
|
|
|
|
|
|
|
|
|
| |
Commit 76a9c3c4be10b3d4d379d5b23ca76806bbae536a renamed DarwinSSL to the
more correct/common name Secure Transport, but a few mentions in the docs
remained.
Closes #5688
Reviewed-by: Daniel Stenberg <daniel@haxx.se>
|
|
|
|
|
|
|
|
|
| |
... by adding support for a new dedicated return code.
Suggested-by: Jonathan Cardoso
Assisted-by: Erik Johansson
URL: https://curl.haxx.se/mail/lib-2020-06/0099.html
Closes #5636
|
|
|
|
|
|
| |
Gets the CURLINFO_EFFECTIVE_METHOD from libcurl.
Added test 1197 to verify.
|
|
|
|
|
|
|
| |
Provide the HTTP method that was used on the latest request, which might
be relevant for users when there was one or more redirects involved.
Closes #5511
|
|
|
|
|
|
|
| |
Reviewed-by: Marcel Raad
Reviewed-by: Marc Hörsken
Closes #5491
|
|
|
|
|
|
|
|
|
| |
include zstd curl patch for Makefile.m32 from vszakats
and include Add CMake support for zstd from Peter Wu
Helped-by: Viktor Szakats
Helped-by: Peter Wu
Closes #5453
|
|
|
|
| |
Closes https://github.com/curl/curl/pull/5655
|
|
|
|
|
|
|
| |
This came up in #5640. It make sense to clarify this in the docs!
Reminded-by: Kamil Dudka
Closes #5642
|
| |
|