delta/curl.git/src/tool_help.c, branch bagder/https-proxy-tests github.com: bagder/curl.git tool: shorten 3 --help descriptions 2020-05-13T14:37:22+00:00 Daniel Stenberg daniel@haxx.se 2020-05-12T07:13:43+00:00 cd3537116342d43e78c8648ca744ad97ebca075f --happy-eyeballs-timeout-ms, --resolve and --ssl-revoke-best-effort gen.pl already warned about these lines but we didn't listen Closes #5379 
--happy-eyeballs-timeout-ms, --resolve and --ssl-revoke-best-effort

gen.pl already warned about these lines but we didn't listen

Closes #5379
retry-all-errors.d: Shorten the summary line 2020-05-12T07:12:55+00:00 Jay Satiro raysatiro@yahoo.com 2020-05-12T07:12:13+00:00 79d60a928218cd117d76aa5019b77702f29a17a1 Follow-up to b995bb5 from a few moments ago. Reported-by: Daniel Stenberg Ref: https://github.com/curl/curl/commit/b995bb5#r39108929 
Follow-up to b995bb5 from a few moments ago.

Reported-by: Daniel Stenberg

Ref: https://github.com/curl/curl/commit/b995bb5#r39108929
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
curl.h: remnove CURL_VERSION_ESNI. Never supported nor documented 2020-03-29T21:28:49+00:00 Daniel Stenberg daniel@haxx.se 2020-03-27T23:00:27+00:00 93fafb93dbd3a5c27ef9a497256df86f9a6670f8 Considered experimental and therefore we can do this. Closes #5157 
Considered experimental and therefore we can do this.

Closes #5157
docs/make: generate curl.1 from listed files only 2020-03-26T12:25:59+00:00 Daniel Stenberg daniel@haxx.se 2020-03-25T22:16:28+00:00 361d4f3fdcd613a78213f38040985fd70022055e Previously it rendered the page from files matching "*.d" in the correct directory, which worked fine in git builds when the files were added but made it easy to forget adding the files to the dist. Now, only man page sections listed in DPAGES in Makefile.inc will be used, thus "forcing" us to update this to get the man page right and get it included in the dist at the same time. Ref: #5146 Closes #5149 
Previously it rendered the page from files matching "*.d" in the correct
directory, which worked fine in git builds when the files were added but
made it easy to forget adding the files to the dist.

Now, only man page sections listed in DPAGES in Makefile.inc will be
used, thus "forcing" us to update this to get the man page right and get
it included in the dist at the same time.

Ref: #5146
Closes #5149
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
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: two new command line options for etags 2019-11-28T12:05:20+00:00 Maros Priputen maros.priputen@student.tuke.sk 2019-10-30T08:43:14+00:00 18e5cb77e986911063da8ab6bf254d632b2de6ea --etag-compare and --etag-save Suggested-by: Paul Hoffman Fixes #4277 Closes #4543 
--etag-compare and --etag-save

Suggested-by: Paul Hoffman
Fixes #4277
Closes #4543
curl: add --parallel-immediate 2019-11-21T15:36:10+00:00 Daniel Stenberg daniel@haxx.se 2019-10-17T08:05:53+00:00 215baa74f709cd5026ea037eb9204cee93baa1bb Starting with this change when doing parallel transfers, without this option set, curl will prefer to create new transfers multiplexed on an existing connection rather than creating a brand new one. --parallel-immediate can be set to tell curl to prefer to use new connections rather than to wait and try to multiplex. libcurl-wise, this means that curl will set CURLOPT_PIPEWAIT by default on parallel transfers. Suggested-by: Tom van der Woerdt Closes #4500 
Starting with this change when doing parallel transfers, without this
option set, curl will prefer to create new transfers multiplexed on an
existing connection rather than creating a brand new one.

--parallel-immediate can be set to tell curl to prefer to use new
connections rather than to wait and try to multiplex.

libcurl-wise, this means that curl will set CURLOPT_PIPEWAIT by default
on parallel transfers.

Suggested-by: Tom van der Woerdt
Closes #4500
docs: document it as --no-progress-meter instead of the reverse 2019-10-09T08:07:02+00:00 Daniel Stenberg daniel@haxx.se 2019-10-08T21:05:35+00:00 9e03faccc3d4b64b09061aeebda8270e27d9ed86 Follow-up to 93373a960c3bb4 Reported-by: infinnovation-dev on github Fixes #4474 Closes #4475 
Follow-up to 93373a960c3bb4

Reported-by: infinnovation-dev on github
Fixes #4474
Closes #4475