summaryrefslogtreecommitdiff
path: root/docs/libcurl/opts
Commit message (Collapse)AuthorAgeFilesLines
* OpenSSL: have CURLOPT_CRLFILE imply CURLSSLOPT_NO_PARTIALCHAINDaniel Stenberg2020-05-131-5/+8
| | | | | | | | ... to avoid an OpenSSL bug that otherwise makes the CRL check to fail. Reported-by: Michael Kaufmann Fixes #5374 Closes #5376
* CURLOPT_SSL_OPTIONS: add *_NATIVE_CA to use Windows CA store (with openssl)Gilles Vollant2020-05-081-0/+4
| | | | Closes #4346
* doc: add missing closing parenthesis in CURLINFO_SSL_VERIFYRESULT.3Emil Engler2020-05-021-1/+1
| | | | Closes #5320
* GnuTLS: Backend support for CURLINFO_SSL_VERIFYRESULTEmil Engler2020-04-301-1/+1
| | | | Closes #5287
* mqtt: add new experimental protocolBjorn Stenberg2020-04-141-1/+1
| | | | Closes #5173
* CURLOPT_WRITEFUNCTION.3: add inline example and new see-alsoDaniel Stenberg2020-04-071-4/+33
| | | | Closes #5192
* CURLINFO_CONDITION_UNMET: return true for 304 http status codeKwon-Young Choi2020-04-051-2/+4
| | | | | | | | | | | In libcurl, CURLINFO_CONDITION_UNMET is used to avoid writing to the output file if the server did not transfered a file based on time condition. In the same manner, getting a 304 HTTP response back from the server, for example after passing a custom If-Match-* header, also fulfill this condition. Fixes #5181 Closes #5183
* copyright: fix out-of-date copyright ranges and missing headersDaniel Stenberg2020-03-2494-92/+134
| | | | | | | | | Reported by the new script 'scripts/copyright.pl'. The script has a regex whitelist for the files that don't need copyright headers. Removed three (mostly usesless) README files from docs/ Closes #5141
* schannel: add "best effort" revocation check optionJohannes Schindelin2020-03-182-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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
* docs: add warnings about FILE: URLs on WindowsDaniel Stenberg2020-03-131-1/+5
| | | | | | | | - --url man page section - libcurl-security.3 gets the full text - CURLOPT_URL.3 Reported-by: Tim Sedlmeyer
* polarssl: remove more references and mentionsDaniel Stenberg2020-03-052-12/+9
| | | | | | Assisted-by: Jay Satiro Follow-up to 6357a19ff29dac04 Closes #5036
* docs: fix typo on CURLINFO_RETRY_AFTER - alwaus -> alwaysJonathan Cardoso Machado2020-02-291-1/+1
| | | | | Reviewed-by: Steve Holme Closes #5005
* CURLOPT_REDIR_PROTOCOLS.3: update the DEFAULT sectionDaniel Stenberg2020-02-181-2/+5
| | | | | | | | to be in sync with the description above Reported-by: Joonas Kuorilehto Fixes #4943 Closes #4945
* CURLINFO_COOKIELIST.3: Fix exampleJay Satiro2020-02-151-3/+3
| | | | | | | | | Prior to this change the example would try to import cookies from stdin, which wasn't what was intended. Reported-by: 3dyd@users.noreply.github.com Fixes https://github.com/curl/curl/issues/4930
* CURLOPT_ALTSVC_CTRL.3: fix the DEFAULT wordingDaniel Stenberg2020-02-111-2/+5
| | | | | | | Assisted-by: Jay Satiro Reported-by: Craig Andrews Fixes #4909 Closes #4910
* location.d: the method change is from POST to GET onlyDaniel Stenberg2020-01-281-2/+2
| | | | | | | | Not from generic non-GET to GET. Reported-by: Andrius Merkys Ref: #4859 Closes #4861
* CURLOPT_PROXY_SSL_OPTIONS.3: Sync with CURLOPT_SSL_OPTIONS.3Jay Satiro2020-01-231-16/+22
| | | | | | | - Copy CURLOPT_SSL_OPTIONS.3 description to CURLOPT_PROXY_SSL_OPTIONS.3. Prior to this change CURLSSLOPT_NO_PARTIALCHAIN was missing from the CURLOPT_PROXY_SSL_OPTIONS description.
* smtp: Allow RCPT TO command to fail for some recipientsPavel Volgarev2020-01-212-0/+72
| | | | | | | | Introduces CURLOPT_MAIL_RCPT_ALLLOWFAILS. Verified with the new tests 3002-3007 Closes #4816
* HTTP: increase EXPECT_100_THRESHOLD to 1Mb加藤郁之2020-01-201-2/+2
| | | | | | Mentioned: https://curl.haxx.se/mail/lib-2020-01/0050.html Closes #4814
* HTTP-COOKIES.md: describe the cookie file formatDaniel Stenberg2020-01-132-2/+10
| | | | | | | | | | ... and refer to that file from from CURLOPT_COOKIEFILE.3 and CURLOPT_COOKIELIST.3 Assisted-by: Jay Satiro Reported-by: bsammon on github Fixes #4805 Closes #4806
* CURLOPT_READFUNCTION.3: fix fopen params in exampleJay Satiro2020-01-061-1/+1
|
* CURLOPT_READFUNCTION.3: fix variable name in exampleJay Satiro2020-01-061-1/+1
| | | | | | Reported-by: Paul Joyce Fixes https://github.com/curl/curl/issues/4787
* CURLOPT_HEADERFUNCTION.3: Document that size is always 1Jay Satiro2019-12-261-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | For compatibility with `fwrite`, the `CURLOPT_HEADERFUNCTION` callback is passed two `size_t` parameters which, when multiplied, designate the number of bytes of data passed in. In practice, CURL always sets the first parameter (`size`) to 1. This practice is also enshrined in documentation and cannot be changed in future. The documentation states that the default callback is `fwrite`, which means `fwrite` must be a suitable function for this purpose. However, the documentation also states that the callback must return the number of *bytes* it successfully handled, whereas ISO C `fwrite` returns the number of items (each of size `size`) which it wrote. The only way these numbers can be equal is if `size` is 1. Since `size` is 1 and can never be changed in future anyway, document that fact explicitly and let users rely on it. Reported-by: Frank Gevaerts Commit-message-by: Christopher Head Ref: https://github.com/curl/curl/pull/2787 Fixes https://github.com/curl/curl/issues/4758
* CURLOPT_QUOTE.3: fix typosJay Satiro2019-12-183-11/+11
| | | | | | | | | Prior to this change the EXAMPLE in the QUOTE/PREQUOTE/POSTQUOTE man pages would not compile because a variable name was incorrect. Reported-by: Bylon2@users.noreply.github.com Fixes https://github.com/curl/curl/issues/4736
* CURLOPT_URL.3: "curl supports SMB version 1 (only)"Daniel Stenberg2019-12-181-2/+2
| | | | [skip ci]
* docs: TLS SRP doesn't work with TLS 1.3Daniel Stenberg2019-12-163-5/+11
| | | | | | Reported-by: sayrer on github Closes #4262 [skip ci]
* CURLOPT_VERBOSE.3: see also ERRORBUFFERDaniel Stenberg2019-12-041-1/+2
|
* openssl: CURLSSLOPT_NO_PARTIALCHAIN can disable partial cert chainsDaniel Stenberg2019-12-031-17/+21
| | | | Closes #4655
* OPENSOCKETFUNCTION.3: correct the purpose descriptionDaniel Stenberg2019-12-031-7/+4
| | | | | | | Reported-by: Jeff Mears Bug: https://curl.haxx.se/mail/lib-2019-12/0007.html Closes #4667
* XFERINFOFUNCTION: support CURL_PROGRESSFUNC_CONTINUEJohn Schroeder2019-11-262-4/+10
| | | | | | | | | (also for PROGRESSFUNCTION) By returning this value from the callback, the internal progress function call is still called afterward. Closes #4599
* copyrights: update all copyright notices to 2019 on files changed this yearVilhelm Prytz2019-11-0215-15/+15
| | | | Closes #4547
* CURLOPT_TIMEOUT.3: Clarify transfer timeout time includes queue timeJay Satiro2019-10-161-5/+6
| | | | | | | | | | | | Prior to this change some users did not understand that the "request" starts when the handle is added to the multi handle, or probably they did not understand that some of those transfers may be queued and that time is included in timeout. Reported-by: Jeroen Ooms Fixes https://github.com/curl/curl/issues/4486 Closes https://github.com/curl/curl/pull/4489
* CURLOPT_TIMEOUT.3: remove the mention of "minutes"Daniel Stenberg2019-10-071-4/+4
| | | | | | | | | ... just say that limiting operations risk aborting otherwise fine working transfers. If that means seconds, minutes or hours, we leave to the user. Reported-by: Martin Gartner Closes #4469
* CURLMOPT_MAX_CONCURRENT_STREAMS.3: fix SEE ALSO typoDaniel Stenberg2019-10-031-1/+1
|
* CURLMOPT_MAX_CONCURRENT_STREAMS: new setoptKunal Ekawde2019-10-022-4/+61
| | | | Closes #4410
* docs: remove trailing ':' from section names in CURLOPT_TRAILER* manAlessandro Ghedini2019-09-152-13/+13
|
* docs: fix typo in CURLOPT_HTTP_VERSION manAlessandro Ghedini2019-09-151-1/+1
|
* CURLOPT_HEADERFUNCTION.3: clarifyChristopher Head2019-08-281-1/+4
| | | | Closes #4273
* CURLINFO docs: mention that in redirects times are addedDaniel Stenberg2019-08-2812-12/+37
| | | | | | Suggested-by: Brandon Dong Fixes #4250 Closes #4269
* CURLOPT_SSL_VERIFYHOST: treat the value 1 as 2Daniel Stenberg2019-08-202-9/+20
| | | | | | | | For a long time (since 7.28.1) we've returned error when setting the value to 1 to make applications notice that we stopped supported the old behavior for 1. Starting now, we treat 1 and 2 exactly the same. Closes #4241
* CURLOPT_ALTSVC.3: use a "" file name to not load from a fileDaniel Stenberg2019-08-141-0/+2
|
* CURLOPT_ALTSVC_CTRL.3: remove CURLALTSVC_ALTUSEDDaniel Stenberg2019-08-131-5/+2
| | | | Follow-up to 98c3f148 that removed it from the header file
* CURLOPT_READFUNCTION.3: provide inline exampleDaniel Stenberg2019-08-121-2/+31
| | | | ... instead of mentioning one in another place
* CURLOPT_H3: removedDaniel Stenberg2019-08-093-60/+2
| | | | | | There's no use for this anymore and it was never in a release. Closes #4206
* CURLOPT_HTTP_VERSION: seting this to 3 forces HTTP/3 use directlyDaniel Stenberg2019-08-083-11/+16
| | | | | | | | | | | | Even though it cannot fall-back to a lower HTTP version automatically. The safer way to upgrade remains via CURLOPT_ALTSVC. CURLOPT_H3 no longer has any bits that do anything and might be removed before we remove the experimental label. Updated the curl tool accordingly to use "--http3". Closes #4197
* CURLINFO_RETRY_AFTER: parse the Retry-After header valueDaniel Stenberg2019-08-072-0/+64
| | | | | | | | This is only the libcurl part that provides the information. There's no user of the parsed value. This change includes three new tests for the parser. Ref: #3794
* sasl: Implement SASL authorisation identity via CURLOPT_SASL_AUTHZIDSteve Holme2019-08-062-0/+65
| | | | | | | | | | | | | | | | | Added the ability for the calling program to specify the authorisation identity (authzid), the identity to act as, in addition to the authentication identity (authcid) and password when using SASL PLAIN authentication. Fixes #3653 Closes #3790 NOTE: This commit was cherry-picked and is part of a series of commits that added the authzid feature for upcoming 7.66.0. The series was temporarily reverted in db8ec1f so that it would not ship in a 7.65.x patch release. Closes https://github.com/curl/curl/pull/4186
* http09: disable HTTP/0.9 by default in both tool and libraryDaniel Stenberg2019-08-061-5/+5
| | | | | | | | As the plan has been laid out in DEPRECATED. Update docs accordingly and verify in test 1174. Now requires the option to be set to allow HTTP/0.9 responses. Closes #4191
* HTTP: use chunked Transfer-Encoding for HTTP_POST if size unknownBalazs Kovacsics2019-07-291-2/+3
| | | | | | | | | If using the read callback for HTTP_POST, and POSTFIELDSIZE is not set, automatically add a Transfer-Encoding: chunked header, same as it is already done for HTTP_PUT, HTTP_POST_FORM and HTTP_POST_MIME. Update test 1514 according to the new behaviour. Closes #4138
* HTTP3: initial (experimental) supportDaniel Stenberg2019-07-212-0/+62
| | | | | | | | | USe configure --with-ngtcp2 or --with-quiche Using either option will enable a HTTP3 build. Co-authored-by: Alessandro Ghedini <alessandro@ghedini.me> Closes #3500
View Lorry Controller Status