| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
... the timer *does* include the instructions for getting the remote
file.
Ref: #6452
Closes #6453
|
|
|
|
|
|
| |
... when built without -DUNICODE.
Closes #6457
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a batch file is run without CRLF line endings (ie LF-only) then
arbitrary behavior may occur. I consider that a bug in Windows, however
the effects can be serious enough (eg unintended code executed) that
we're fixing it in the repo by requiring CRLF line endings for batch
files on checkout.
Prior to this change the checked-out line endings of batch files were
dependent on a user's git preferences. On Windows it is common for git
users to have automatic CRLF conversion enabled (core.autocrlf true),
but those users that don't would run into this behavior.
For example a user has reported running the Visual Studio project
generator batch file (projects/generate.bat) and it looped forever.
Output showed that the Windows OS interpreter was occasionally jumping
to arbitrary points in the batch file and executing commands. This
resulted in unintended files being removed (a removal sequence called)
and looping forever.
Ref: https://serverfault.com/q/429594
Ref: https://stackoverflow.com/q/232651
Ref: https://www.dostips.com/forum/viewtopic.php?t=8988
Ref: https://git-scm.com/docs/gitattributes#_checking_out_and_checking_in
Ref: https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#_core_autocrlf
Bug: https://github.com/curl/curl/discussions/6427
Reported-by: Ganesh Kamath
Closes https://github.com/curl/curl/pull/6442
|
| |
|
|
|
|
|
|
| |
o removed HSTS - already implemented
o added HTTPS RR records
o mention HTTP/3 completion
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
... as we reserve this prefix to library-wide functions.
Closes #6443
|
|
|
|
| |
Closes #6445
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Move Windows terminal init code from tool_main to tool_doswin.
- Restore the original console settings on CTRL+C and CTRL+BREAK.
Background: On Windows the curl tool changes the console settings to
enable virtual terminal processing (eg color output) if supported
(ie Win 10). The original settings are restored on exit but prior to
this change were not restored in the case of the CTRL signals.
Windows VT behavior varies depending on console/powershell/terminal;
refer to the discussion in #6226.
Assisted-by: Rich Turner
Closes https://github.com/curl/curl/pull/6226
|
|
|
|
| |
Follow-up to 324cf1d2e
|
|
|
|
|
|
| |
This commit bumps the help to the current state of the project.
Closes #6437
|
|
|
|
|
|
|
|
|
| |
The script warns if the length of $opt and $desc is > 78. However, these
two variables are on totally separate lines so the check makes no sense.
Also the $bitmask field is totally forgotten. Currently this leads to
two warnings within `--resolve` and `--aws-sigv4`.
Closes #6438
|
|
|
|
|
|
|
| |
curl does not list all categories when you invoke "--help" without any
parameters.
Closes #6436
|
|
|
|
|
|
| |
Make it shorter and imperative form
Closes #6439
|
|
|
|
|
| |
Bug: https://curl.se/mail/lib-2021-01/0063.html
Closes #6434
|
|
|
|
|
|
|
| |
As that's a significant error condition and scan-build warns for NULL
pointer dereferences if we don't.
Closes #6433
|
|
|
|
| |
... to avoid running in that state with data->conn being NULL.
|
|
|
|
| |
Detected by scan-build
|
|
|
|
|
|
| |
Pointed out by Coverity
Closes #6431
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- During the end-of-headers response phase do not mark the tunnel
complete unless the response body was completely parsed/ignored.
Prior to this change if the entirety of a CONNECT response with chunked
encoding was not received by the time the final header was parsed then
the connection would be marked done prematurely, before all the chunked
data could be read in and ignored (since this is what we do with any
CONNECT response body) and the connection could not be used.
Bug: https://curl.se/mail/lib-2021-01/0033.html
Reported-by: Fabian Keil
Closes https://github.com/curl/curl/pull/6432
|
| |
|
|
|
|
|
|
|
|
| |
This improves IDNA2003 compatiblity.
Reported-by: Bubu on github
Fixes #6423
Closes #6428
|
|
|
|
| |
Closes #6430
|
|
|
|
|
|
|
| |
When doing a request with a request body expecting a 401/407 back, that
initial request is sent with a zero content-length. Test 177 and more.
Closes #6424
|
|
|
|
|
|
|
|
|
|
| |
New option USE_LIBIDN2 defaults to ON for libidn2 detection. Prior to
this change libidn2 detection could not be turned off in cmake builds.
Reported-by: William A Rowe Jr
Fixes https://github.com/curl/curl/issues/6361
Closes https://github.com/curl/curl/pull/6362
|
| |
|
|
|
|
| |
... to make "Hyper mode" work better.
|
|
|
|
|
|
|
| |
... as it is misleading.
Ref #6379
Closes #6421
|
|
|
|
| |
Ref #6379
|
|
|
|
|
|
|
| |
Follow-up to a1f06f32b860, to make sure it can be handled separately
from plain gopher.
Closes #6418
|
|
|
|
|
|
|
|
|
|
| |
... so that Retry-After and other meta-content can still be used.
Added 1634 to verify. Adjusted test 194 and 281 since --fail now also
includes the header-terminating CRLF in the output before it exits.
Fixes #6408
Closes #6409
|
|
|
|
|
|
|
|
|
|
| |
... to make build tools/valgrind warn if no curl_global_cleanup is
called.
This is conditionally only done for debug builds with the env variable
CURL_GLOBAL_INIT set.
Closes #6410
|
| |
|
|
|
|
| |
Closes #6419
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... and not in the connection setup, as for multiplexed transfers the
connection setup might be skipped and then the transfer would end up
without the set user-agent!
Reported-by: Flameborn on github
Assisted-by: Andrey Gursky
Assisted-by: Jay Satiro
Assisted-by: Mike Gelfand
Fixes #6312
Closes #6417
|
|
|
|
| |
...as Hyper doesn't support HTTP/0.9
|
|
|
|
|
|
| |
... makes test 36 work.
Closes #6412
|
|
|
|
|
|
|
| |
Printing trust purposes are now sorted, making the output deterministic
when running on the same input certdata.txt.
Closes #6413
|