| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Follow-up to 9e5669f3880674
Detected by Coverity CID 1464582 ("Logically dead code")
|
| |
|
|
|
|
|
|
| |
For QUIC but also for regular TCP when the second family runs out of IPs
with a failure while the first family is still trying to connect.
Separated the timeout handling for IPv4 and IPv6 connections when they
both have a number of addresses to iterate over.
|
| | |
|
| |
|
|
|
|
| |
Reported-by: Peter Wu
Fixes #5565
Closes #5568
|
| |
|
|
| |
Closes #5573
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This avoids using a pair of TCP ports to provide wakeup functionality
for every multi instance on Windows, where socketpair() is emulated
using a TCP socket on loopback which could in turn lead to socket
resource exhaustion.
Reviewed-by: Gergely Nagy
Reviewed-by: Marc Hörsken
Closes #5397
|
| |
|
|
|
|
| |
CURL_SSL_BACKEND, QLOGDIR and SSLKEYLOGFILE
Closes #5571
|
| | |
|
| |
|
|
| |
Also adds pkg-config support for the wolfSSL detection.
|
| |
|
|
|
|
|
|
|
| |
When wolfSSL is built with its OpenSSL API layer, it fetures the same DES*
functions that OpenSSL has. This change take advantage of that.
Co-authored-by: Daniel Stenberg
Closes #5556
Fixes #5548
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Since the connection can be used by many independent requests (using
HTTP/2 or HTTP/3), things like user-agent and other transfer-specific
data MUST NOT be kept connection oriented as it could lead to requests
getting the wrong string for their requests. This struct data was
lingering like this due to old HTTP1 legacy thinking where it didn't
mattered..
Fixes #5566
Closes #5567
|
| |
|
|
|
|
|
|
|
|
|
| |
Assisted-by: Daniel Gustafsson
Assisted-by: Rich Salz
Assisted-by: Hugo van Kemenade
Assisted-by: James Fuller
Assisted-by: Marc Hörsken
Assisted-by: Jay Satiro
Closes #5555
|
| |
|
|
|
|
|
|
| |
It was superfluous since we have the list.size alredy
Reported-by: Jay Satiro
Fixes #5553
Closes #5563
|
| |
|
|
|
|
|
| |
Added a few missing features not previously mentioned. Ordered them
alphabetically.
Closes #5558
|
| |
|
|
| |
Closes #5562
|
| |
|
|
|
|
|
|
|
|
| |
The point of this section is to meet the CII Best Practices gold level
critera:
"The project MUST clearly identify small tasks that can be performed by
new or casual contributors"
Closes #5560
|
| |
|
|
| |
Closes #5462
|
| | |
|
| |
|
|
|
|
|
| |
Follow-up to ad6416986755e417c66e2c6, which caused wrong formatting on
curl documentation website
Closes #5561
|
| |
|
|
| |
Closes #5549
|
| |
|
|
|
|
|
|
| |
When asking for a specific feature to be shared in the share object,
that bit was previously set unconditionally even if the shared feature
failed or otherwise wouldn't work.
Closes #5554
|
| |
|
|
| |
It's just too annoying and unnecessary to get a long list of files shown
|
| | |
|
| |
|
|
|
|
|
|
| |
Instead of discussing if there's value or meaning (implied or not) in
the colors, let's use words without the same possibly negative
associations.
Closes #5546
|
| |
|
|
|
|
|
|
|
| |
Prior to this change in Windows Unicode builds most parsed options would
not be freed.
Found using _CrtDumpMemoryLeaks().
Ref: https://github.com/curl/curl/issues/5545
|
| |
|
|
|
|
|
|
|
| |
The SOCKS4/5 state machines weren't properly terminated when the proxy
connection got closed, leading to a busy-loop.
Reported-By: zloi-user on github
Fixes #5532
Closes #5542
|
| |
|
|
| |
Closes #5540
|
| |
|
|
|
|
|
|
| |
To reduce the amount of allocations needed for creating a Curl_addrinfo
struct, make a single larger malloc instead of three separate smaller
ones.
Closes #5533
|
| |
|
|
|
|
|
|
| |
quiche now requires the application to explicitly set the keylog path
for each connection, rather than reading the environment variable
itself.
Closes #5541
|
| |
|
|
|
|
| |
Test 895 and 896 - as a follow-up to a3e972313b
Closes #5539
|
| |
|
|
|
|
|
| |
Syncs with ngtcp2 commit 7e9a917d386d98 merged June 7 2020.
Assisted-by: Tatsuhiro Tsujikawa
Closes #5538
|
| |
|
|
| |
Closes #5537
|
| |
|
|
|
|
|
| |
Memory leak
Reported-by: Geeknik Labs
Fixes #5535
Closes #5536
|
| |
|
|
|
|
|
| |
Remove weird work-around for storing the SFTP errors as int instead of
the "unsigned long" that libssh2 actually returns for SFTP errors.
Closes #5534
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Now that all functions in select.[ch] take timediff_t instead
of the limited int or long, we can remove type conversions
and related preprocessor checks to silence compiler warnings.
Avoiding conversions from time_t was already done in 842f73de.
Based upon #5262
Supersedes #5214, #5220 and #5221
Follow up to #5343 and #5479
Closes #5490
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
On some systems, openssl 1.0.x is still the default, but it has been
patched to contain all the recent security fixes. As a result of this
patching, it is possible for macro X509_V_FLAG_NO_ALT_CHAINS to be
defined, while the previous behavior of openssl to not look at trusted
chains first, remains.
Fix it: ensure X509_V_FLAG_TRUSTED_FIRST is always set, do not try to
probe for the behavior of openssl based on the existence ofmacros.
Closes #5530
|
| |
|
|
|
|
|
|
|
| |
... this caused segfaults on armv7.
Regression added in dd0365d560aea5a (7.70.0)
Reviewed-by: Jay Satiro
Closes #5529
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Commit 4a4b63d forgot to set the expected SOCKS5 reply length when the
reply ATYP is X'01'. This resulted in erroneously expecting more bytes
when the request length is greater than the reply length (e.g., when
remotely resolving the hostname).
Closes #5527
|
| |
|
|
|
|
| |
Since the new curl/stats repository is designed to be
checked out into the curl repository working tree as stats/
it should be on the ignore list to aid in commit staging.
|
| |
|
|
|
|
| |
Cargo needs to be called from within the 'quiche' directory.
Closes #5522
|
| |
|
|
| |
Closes #5525
|
| |
|
|
|
|
| |
In the continued effort to remove "manual" realloc schemes.
Closes #5524
|
| |
|
|
|
|
| |
Reported-by: Jay Satiro
Fixes #5299
Closes #5520
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the logic that works out if a given OpenSSL path works, it stripped
off a possibly leading -L flag using an incorrect sed pattern which
would remove all instances of -L in the string, including if the path
itself contained that two-letter sequence!
The same pattern was used and is now updated in multiple places. Now it
only removes -L if it starts the strings.
Reported-by: Mohamed Osama
Fixes #5519
Closes #5521
|
