delta/curl.git/src/tool_operate.c, branch bagder/https-proxy-tests github.com: bagder/curl.git tool: Add option --retry-all-errors to retry on any error 2020-05-12T07:00:15+00:00 Jay Satiro raysatiro@yahoo.com 2020-04-04T20:16:18+00:00 b995bb58cbd976280b132ee2148376fadd071063 The "sledgehammer" of retrying. Closes https://github.com/curl/curl/pull/5185 
The "sledgehammer" of retrying.

Closes https://github.com/curl/curl/pull/5185
tool_operate: only set CURLOPT_SSL_OPTIONS if SSL support is present 2020-05-10T13:33:51+00:00 Daniel Stenberg daniel@haxx.se 2020-05-10T09:51:42+00:00 6f63ab41b2949ad9819efb0f585122b880cd55ba Reported-by: Marcel Raad Follow-up to 148534db5 Fixes #5367 Closes #5369 
Reported-by: Marcel Raad
Follow-up to 148534db5
Fixes #5367
Closes #5369
CURLOPT_SSL_OPTIONS: add *_NATIVE_CA to use Windows CA store (with openssl) 2020-05-08T13:55:04+00:00 Gilles Vollant info@winimage.com 2019-09-13T09:24:00+00:00 148534db57dda611cf8516e92e4d6e35fc1e5074 Closes #4346 
Closes #4346
curl: allow both --etag-compare and --etag-save with same file name 2020-04-04T23:07:52+00:00 Kwon-Young Choi kwon-young.choi@hotmail.fr 2020-04-03T18:51:14+00:00 a448a4ce2615373fc63818afede79550f2ca6a14 This change inverse the order of processing for the --etag-compare and --etag-save option to process first --etag-compare. This in turn allows to use the same file name to compare and save an etag. The original behavior of not failing if the etag file does not exists is conserved. Fixes #5179 Closes #5180 
This change inverse the order of processing for the --etag-compare and
--etag-save option to process first --etag-compare. This in turn allows
to use the same file name to compare and save an etag.

The original behavior of not failing if the etag file does not exists is
conserved.

Fixes #5179
Closes #5180
build: fixed build for systems with select() in unistd.h 2020-03-31T08:59:06+00:00 Harry Sintonen sintonen@iki.fi 2020-03-30T13:52:43+00:00 7a71965e9761f80aa4508472c5b1e3ab03ba018a Closes #5169 
Closes #5169
schannel: add "best effort" revocation check option 2020-03-18T07:23:39+00:00 Johannes Schindelin johannes.schindelin@gmx.de 2020-02-26T10:24:26+00:00 54504284918a4ba19bc7b1efb486a64629d376aa - Implement new option CURLSSLOPT_REVOKE_BEST_EFFORT and --ssl-revoke-best-effort to allow a "best effort" revocation check. A best effort revocation check ignores errors that the revocation check was unable to take place. The reasoning is described in detail below and discussed further in the PR. --- When running e.g. with Fiddler, the schannel backend fails with an unhelpful error message: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate. Sadly, many enterprise users who are stuck behind MITM proxies suffer the very same problem. This has been discussed in plenty of issues: https://github.com/curl/curl/issues/3727, https://github.com/curl/curl/issues/264, for example. In the latter, a Microsoft Edge developer even made the case that the common behavior is to ignore issues when a certificate has no recorded distribution point for revocation lists, or when the server is offline. This is also known as "best effort" strategy and addresses the Fiddler issue. Unfortunately, this strategy was not chosen as the default for schannel (and is therefore a backend-specific behavior: OpenSSL seems to happily ignore the offline servers and missing distribution points). To maintain backward-compatibility, we therefore add a new flag (`CURLSSLOPT_REVOKE_BEST_EFFORT`) and a new option (`--ssl-revoke-best-effort`) to select the new behavior. Due to the many related issues Git for Windows and GitHub Desktop, the plan is to make this behavior the default in these software packages. The test 2070 was added to verify this behavior, adapted from 310. Based-on-work-by: georgeok <giorgos.n.oikonomou@gmail.com> Co-authored-by: Markus Olsson <j.markus.olsson@gmail.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Closes https://github.com/curl/curl/pull/4981 
- Implement new option CURLSSLOPT_REVOKE_BEST_EFFORT and
  --ssl-revoke-best-effort to allow a "best effort" revocation check.

A best effort revocation check ignores errors that the revocation check
was unable to take place. The reasoning is described in detail below and
discussed further in the PR.

---

When running e.g. with Fiddler, the schannel backend fails with an
unhelpful error message:

	Unknown error (0x80092012) - The revocation function was unable
	to check revocation for the certificate.

Sadly, many enterprise users who are stuck behind MITM proxies suffer
the very same problem.

This has been discussed in plenty of issues:
https://github.com/curl/curl/issues/3727,
https://github.com/curl/curl/issues/264, for example.

In the latter, a Microsoft Edge developer even made the case that the
common behavior is to ignore issues when a certificate has no recorded
distribution point for revocation lists, or when the server is offline.
This is also known as "best effort" strategy and addresses the Fiddler
issue.

Unfortunately, this strategy was not chosen as the default for schannel
(and is therefore a backend-specific behavior: OpenSSL seems to happily
ignore the offline servers and missing distribution points).

To maintain backward-compatibility, we therefore add a new flag
(`CURLSSLOPT_REVOKE_BEST_EFFORT`) and a new option
(`--ssl-revoke-best-effort`) to select the new behavior.

Due to the many related issues Git for Windows and GitHub Desktop, the
plan is to make this behavior the default in these software packages.

The test 2070 was added to verify this behavior, adapted from 310.

Based-on-work-by: georgeok <giorgos.n.oikonomou@gmail.com>
Co-authored-by: Markus Olsson <j.markus.olsson@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Closes https://github.com/curl/curl/pull/4981
tool_operate: fix add_parallel_transfers when more are in queue 2020-03-16T08:51:34+00:00 Daniel Stenberg daniel@haxx.se 2020-03-16T08:33:27+00:00 95c36fff75883ace6e8e7a89b94362de2dd1857f Trying to return early from the function if no new transfers were added would break the "morep" argument and cause issues. This could lead to zero content "transfers" (within quotes since they would never be started) when parallel-max was reduced. Reported-by: Gavin Wong Analyzed-by: Jay Satiro Fixes #4937 Closes #5112 
Trying to return early from the function if no new transfers were added
would break the "morep" argument and cause issues. This could lead to
zero content "transfers" (within quotes since they would never be
started) when parallel-max was reduced.

Reported-by: Gavin Wong
Analyzed-by: Jay Satiro
Fixes #4937
Closes #5112
curl: error on --alt-svc use w/o support 2020-02-05T06:57:38+00:00 Daniel Stenberg daniel@haxx.se 2020-02-04T16:32:55+00:00 1cc97ba6e42820ad0d8d69ba101b3b830aa1316d Make the tool check for alt-svc support at run-time and return error accordingly if not present when the option is used. Reported-by: Harry Sintonen Closes #4878 
Make the tool check for alt-svc support at run-time and return error
accordingly if not present when the option is used.

Reported-by: Harry Sintonen
Closes #4878
smtp: Allow RCPT TO command to fail for some recipients 2020-01-21T09:40:19+00:00 Pavel Volgarev pvolgarev@google.com 2020-01-14T22:22:38+00:00 4a4609bf3c812afc65f700b4b7e673cc76ade1bf Introduces CURLOPT_MAIL_RCPT_ALLLOWFAILS. Verified with the new tests 3002-3007 Closes #4816 
Introduces CURLOPT_MAIL_RCPT_ALLLOWFAILS.

Verified with the new tests 3002-3007

Closes #4816
curl: Let -D merge headers in one file again 2020-01-21T08:23:30+00:00 Emil Engler me@emilengler.com 2020-01-21T08:23:21+00:00 1774dbd74c77cd6c728588c8a717903dd16003f3 Closes #4762 Fixes #4753 
Closes #4762
Fixes #4753