| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
To refer to the proper cookie RFC and the upcoming RFC refresh.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Since that header file is the only place that define can be defined.
Reported-by: Marc Deslauriers
Follow-up to 13718030ad4b3209
Closes #11121
|
|
|
|
| |
Closes #11117
|
|
|
|
| |
Closes #11113
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hook the new (1.11.0 or newer) libssh2 support for setting a read timeout
into the SERVER_RESPONSE_TIMEOUT option. With this done, clients can use
the standard curl response timeout setting to also control the time that
libssh2 will wait for packets from a slow server. This is necessary to
enable use of very slow SFTP servers.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
Closes #10965
|
|
|
|
| |
Closes #11110
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
They are marked as deprecated in iOS 13.0, which might result in
warnings-as-errors.
Also, use `*_MIN_REQUIRED` instead of `*_MIN_ALLOWED`, which seems to
be what's currently used.
Bug: https://github.com/curl/curl/issues/11098
Closes https://github.com/curl/curl/pull/11102
|
|
|
|
|
|
|
|
| |
Its only usage in curl_ntlm_core.c is guarded by `USE_CURL_NTLM_CORE`,
so let's use this here too.
Ref: https://github.com/curl/curl/issues/11098
Closes https://github.com/curl/curl/pull/11102
|
|
|
|
| |
Closes #11107
|
|
|
|
| |
Closes #11106
|
|
|
|
|
|
| |
Reproduces the isue #11101 and verifies the fix.
Verifies a17b2a503f
|
|
|
|
|
|
|
|
|
|
| |
The "prevhead" pointer is used for the headers storage but was not
cleared correctly in init, which made it possible to act up when a
handle is reused.
Reported-by: Steve Herrell
Fixes #11101
Closes #11103
|
| |
|
|
|
|
|
|
|
|
|
| |
- nghttp3 0.11.0
- nghttp2 1.53.0
Adapt to new API calls
Closes #11031
|
| |
|
|
|
|
|
|
| |
Follow-up to 9ed7d56e044f5aa1b29
Closes #11096
|
|
|
|
|
|
|
|
|
|
| |
Theoretically, the oldest time could overflow an int. In practice that
won't happen, but let's do this to please analyzers.
Follow-up to 9ed7d56e044f5aa1b2928ccde6245d0
Pointed out by Coverity.
Closes #11094
|
|
|
|
|
|
|
|
| |
To avoid a memory-leak.
Reported-by: Hiroki Kurosawa
Closes #11093
|
|
|
|
|
|
| |
Reported-by: Dylan Anthony
Fixes #11091
Closes #11092
|
|
|
|
|
| |
Reported-by: Wei Chong Tan
Closes #11088
|
|
|
|
|
| |
Reported-by: Harry Sintonen
Closes #11087
|
|
|
|
|
|
|
|
|
|
| |
To reduce the damage an application can cause if using -1 or other
ridiculous timeout values and letting the cache live long times.
The maximum number of entries in the DNS cache is now totally
arbitrarily and hard-coded set to 29999.
Closes #11084
|
|
|
|
|
| |
... because it set and held as an 'int' elsewhere and can never be
larger.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libcurl assumes that a --continue-at resumption is done to continue an
upload using the read callback and neither --data nor --form use
that and thus won't do what the user wants. Whatever the user wants
with this strange combination.
Add test 426 to verify.
Reported-by: Smackd0wn on github
Fixes #11081
Closes #11083
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code assumes that such a resume is wanting to continue an upload
using the read callback, and since POSTFIELDS is done without callback
libcurl will just misbehave.
This combo will make the transfer fail with CURLE_BAD_FUNCTION_ARGUMENT
with an explanation in the error message.
Reported-by: Smackd0wn on github
Fixes #11081
Closes #11083
|
|
|
|
|
|
|
|
| |
... which for example means they do not have --no-* versions.
Reported-by: Harry Sintonen
Fixes #11085
Closes #11086
|
|
|
|
| |
Closes #11080
|
|
|
|
| |
Closes #11077
|
|
|
|
|
|
|
|
|
|
| |
The curl binary argument wasn't being quoted properly. This seems to
have broken at some point after quoting was added in commit 606b29fe.
Reported-by: Daniel Stenberg
Ref: #11073
Fixes #11074
Closes #11076
|
|
|
|
|
|
|
| |
The controller currently only creates and uses one, but more are now
possible.
Ref: #10818
|
|
|
|
|
|
|
|
|
|
|
| |
When the -j option is given, a new process is spawned in which the test
programs are run and from which test servers are started. Only one
process can be started at once, but this is sufficient to test that the
infrastructure can isolate those functions in a new task. There should
be no visible difference between the two modes at the moment.
Ref: #10818
Closes #11064
|
|
|
|
|
|
| |
This allows it to run in a non-blocking manner.
Ref: #10818
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Program arguments are marshalled and then written to the end of a pipe
which is later read from and the arguments unmarshalled before the
desired function is called normally. The function return values are
then marshalled and written into another pipe when is later read from
and unmarshalled before being returned to the caller.
The implementation is currently blocking but can be made non-blocking
without any changes to the API. This allows calling multiple runners
without blocking in the future.
Ref: #10818
|
|
|
|
|
|
| |
This is where citest_starttest is called.
Ref: #10818
|
|
|
|
|
|
| |
This sets up the runner environment to start running tests.
Ref: #10818
|
|
|
|
|
|
|
|
| |
There will soon be multiple log directories so the paths will no longer
be static in runtests.pl. Also, get rid of $SERVER2IN which was not
used.
Ref: #10818
|
|
|
|
|
|
|
|
| |
Some recent refactoring made these export no longer necessary. Also,
stop displaying the Unix socket paths at startup since there will soon
be many of them and they're not that interesting.
Ref: #10818
|
|
|
|
|
|
| |
This will no longer be static soon.
Ref: #10818
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Disable hyperlink formatting for the 'Location:' header value in VTE
0.48.1 and earlier, since it is buggy in some of those versions.
Prior to this change those terminals may show the location header value
as gibberish or show it twice.
Ref: https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda#backward-compatibility
Fixes https://github.com/curl/curl/issues/10428
Closes https://github.com/curl/curl/pull/11071
|
|
|
|
| |
Closes #11068
|
|
|
|
|
|
|
|
|
| |
By insisting that the passed in handle is "good" (the magic number is
intact), this can limit the potential damage if a bad pointer is passed
in. Like when this function is called twice on the same handle pointer.
Ref: #10964
Closes #11061
|
|
|
|
|
|
|
| |
AmiSSL stores certificates in `AmiSSL:Certs` and MorphOS stores them in
`MOSSYS:Data/SSL/curl-ca-bundle.crt`.
Closes https://github.com/curl/curl/pull/11059
|
|
|
|
|
|
| |
When h2_progress_egress() is called. Pointed out by Coverity.
Closes #11057
|