| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
and take care of zero-length values, avoiding conversion to base64
and/or trailing spaces.
Closes #8136
|
|
|
|
|
|
|
|
| |
7.61.0 is over three years old now, remove all #ifdefs for handling
ancient libcurl versions so that the example gets easier to read and
understand
Closes #8137
|
|
|
|
| |
Closes #8133
|
|
|
|
| |
Closes #8119
|
| |
|
|
|
|
|
|
|
|
| |
Upon receiving large result sets, this reduces memory consumption and
allows starting to output results while the transfer is still in
progress.
Closes #8101
|
|
|
|
|
|
| |
This makes Curl_hash_init() infallible which saves error paths.
Closes #8132
|
|
|
|
|
|
|
|
|
| |
Since each socket hash entry may themselves have a hash table in them,
the destroying of the socket hash needs to make sure all the subhashes
are also correctly destroyed to avoid leaking memory.
Fixes #8129
Closes #8131
|
|
|
|
|
|
|
|
| |
It is not text mode.
Follow-up to 6f73e68d182
Closes #8134
|
|
|
|
| |
Closes #8128
|
|
|
|
| |
Closes #8128
|
|
|
|
| |
Closes #8128
|
|
|
|
| |
Closes #8128
|
|
|
|
|
|
| |
Minor reorg of the lib1156 code and it works fine for hyper.
Closes #8127
|
|
|
|
| |
Closes #8126
|
|
|
|
|
|
|
|
| |
- remove a lot of exclamation marks
- use consistent spaces (1, not 2)
- use better words at some places
Closes #8123
|
|
|
|
| |
Closes #8125
|
|
|
|
| |
Closes #8124
|
|
|
|
|
|
| |
Repairs test 1140
Follow-up to 436cdf82041
|
| |
|
|
|
|
|
|
|
|
| |
An error returned from one of these funtions mean that ALL still ongoing
transfers are to be considered failed.
Ref: #8114
Closes #8120
|
|
|
|
|
|
| |
Follow-up to #8089 (2b3dd01)
Closes #8116
|
|
|
|
|
|
| |
For example trying to add entries after the hash has been "cleaned up"
Closes #8115
|
|
|
|
|
|
|
|
|
| |
This makes torture tests run more proper.
Also add an assert to trap situations where it would end up with no
sockets to wait for.
Closes #8121
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|