| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
An error returned from one of these funtions mean that ALL still ongoing
transfers are to be considered failed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Minor rephrasing for some explanations.
Put the format strings in stand-alone lines with .nf/.fi to be easier to spot.
Move "added in" to AVAILABILITY
Closed #8110
|
|
|
|
| |
Closes #8105
|
|
|
|
| |
Closes #8104
|
|
|
|
| |
... as it needs --retry too to work
|
|
|
|
| |
Closes #7980
|
|
|
|
|
|
|
|
|
|
| |
This is the exact same limitation already documented for
CURLOPT_WRITEDATA but should be clarified here. It also has a different
work-around.
Reported-by: Stephane Pellegrino
Bug: https://github.com/curl/curl/issues/8102
Closes #8103
|
|
|
|
|
|
|
|
|
|
|
|
| |
The callbacks were partially documented to support this. Now the
behavior is documented and returning error from either of these
callbacks will effectively kill all currently ongoing transfers.
Added test 530 to verify
Reported-by: Marcelo Juchem
Fixes #8083
Closes #8089
|
|
|
|
|
|
|
|
|
| |
If curl_url() returns NULL this should return early to avoid mistakes -
even if right now the subsequent function invokes are all OK.
Coverity (wrongly) pointed out this as a NULL deref.
Closes #8100
|
|
|
|
|
|
|
| |
Detected by Coverity. CID 1494642.
Follow-up from 2be1aa619bca
Closes #8099
|
|
|
|
|
|
|
|
| |
A 'CURLU *' would leak if url_proto() is called with no URL.
Detected by Coverity. CID 1494643.
Follow-up to 18270893abdb19
Closes #8098
|
|
|
|
|
|
|
| |
As this introduces use of CURLOPT_USE_SSL option for LDAP, also check
this option in ldap.c as it is not supported by this backend.
Closes #8065
|
|
|
|
| |
Closes #8097
|
|
|
|
| |
Closes #8097
|
|
|
|
| |
Follow-up to 172068b76f
|
|
|
|
| |
Closes #8094
|
| |
|
|
|
|
|
|
|
|
| |
Output "3" properly when HTTP/3 was used.
Reported-by: Bernat Mut
Fixes #8072
Closes #8092
|
|
|
|
|
|
|
|
|
|
| |
This is a regression since 7.62.0 (fb30ac5a2d).
Updated test 1560 accordingly
Reported-by: Brad Fitzpatrick
Fixes #8090
Closes #8091
|
|
|
|
| |
Closes #8082
|
|
|
|
|
|
|
| |
The repo repo was re-organized a bit, so the build instructions need to
be updated.
Closes #8076
|
|
|
|
| |
Since we say it is a non-repating timer
|
|
|
|
|
| |
Fixes #8079
Closes #8081
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this change the build number was not checked during version
comparison, and the platform id was supposed to be checked but wasn't.
Checking the build number is required for enabling "evergreen"
Windows 10/11 features (like TLS 1.3).
Ref: https://github.com/curl/curl/pull/7784
Closes https://github.com/curl/curl/pull/7824
Closes https://github.com/curl/curl/pull/7867
|
|
|
|
|
|
| |
- On mismatch error show sha256 fingerprint in base64 format.
Prior to this change the fingerprint was mistakenly printed in binary.
|
|
|
|
| |
Closes #8078
|
|
|
|
|
|
| |
Add many more options that can reduce the size of the binary that were
added since the last update. Update the sample minimal binary size for
version 7.80.0.
|
|
|
|
|
| |
These are needed to skip some tests when configure options have disabled
certain features.
|
|
|
|
| |
Closes #8071
|
|
|
|
|
|
|
|
|
| |
https://datatracker.ietf.org/doc/html/rfc7616#section-3.4.4
... the client MUST calculate a hash of the username after
any other hash calculation ...
Signed-off-by: Glenn Strauss <gstrauss@gluelogic.com>
Closes #8066
|
|
|
|
| |
Assisted-by: Jay Satiro
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The homedir() function is now renamed into findfile() and iterates over
all the environment variables trying to access the file in question
until it finds it. Last resort is then getpwuid() if
available. Previously it would first try to find a home directory and if
that was set, insist on checking only that directory for the file. This
now returns the full file name it finds.
The Windows specific checks are now done differently too and in this
order:
1 - %USERPROFILE%
2 - %APPDATA%
3 - %USERPROFILE%\\Application Data
The windows order is modified to match how the Windows 10 ssh tool works
when it searches for .ssh/known_hosts.
Reported-by: jeffrson on github
Co-authored-by: Jay Satiro
Fixes #8033
Closes #8035
|
|
|
|
|
|
|
|
|
|
| |
Make all libcurl related options use .nf (no fill) for the SYNOPSIS
section - for consistent look. roffit then renders that section using
<pre> (monospace font) in html for the website.
Extended manpage-syntax (test 1173) with a basic check for it.
Closes #8062
|
| |
|
|
|
|
| |
Closes #8054
|
|
|
|
|
|
|
|
|
| |
- avoid exclamation marks
- use consistent number of spaces after periods: one
- avoid clichés
- avoid using 'very'
Closes #8060
|
|
|
|
| |
Closes #8059
|
|
|
|
| |
Closes #8058
|
|
|
|
| |
Closes #8056
|
|
|
|
|
|
|
|
|
|
|
|
| |
- accept `-schannel` as an alternative to `CFG` option `-winssl`
(latter still accepted, but deprecated)
- rename internal variable `WINSSL` to `SCHANNEL`
- make the `CFG` option evaluation shorter, without repeating the option
name
Reviewed-by: Marcel Raad
Reviewed-by: Daniel Stenberg
Closes #8053
|
|
|
|
|
| |
Reported-by: David Bohman
Closes #7716
|
|
|
|
|
|
|
|
|
|
| |
- 5.10 SMB tests fail with Python 2
Just use python 3.
+ 5.10 curl hangs on SMB upload over stdin
Closes #7896
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the return code CURLUE_MALFORMED_INPUT was used for almost
30 different URL format violations. This made it hard for users to
understand why a particular URL was not acceptable. Since the API cannot
point out a specific position within the URL for the problem, this now
instead introduces a number of additional and more fine-grained error
codes to allow the API to return more exactly in what "part" or section
of the URL a problem was detected.
Also bug-fixes curl_url_get() with CURLUPART_ZONEID, which previously
returned CURLUE_OK even if no zoneid existed.
Test cases in 1560 have been adjusted and extended. Tests 1538 and 1559
have been updated.
Updated libcurl-errors.3 and curl_url_strerror() accordingly.
Closes #8049
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instad of having all callers pass in the maximum length, always use
it. The passed in length is instead used only as the length of the
target buffer for to storing the scheme name in, if used.
Added the scheme max length restriction to the curl_url_set.3 man page.
Follow-up to 45bcb2eaa78c79
Closes #8047
|
|
|
|
|
|
| |
Follow-up to 9108da2c26d
Closes #8052
|
|
|
|
|
| |
Fixes #8012
Closes #8022
|
|
|
|
|
|
|
|
|
| |
Since the 'CMAKE_' prefix is reserved for cmake's own private use.
Ref: https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html
Reported-by: Boris Rasin
Fixes #7988
Closes #8044
|
|
|
|
|
|
|
|
| |
file URLs that are 6 bytes or shorter are not complete. Return
CURLUE_MALFORMED_INPUT for those. Extended test 1560 to verify.
Triggered by #8041
Closes #8042
|