send: assert that Curl_write_plain() has a ->conn when called

To help catch bad invokes.

Closes #6476

test410: verify HTTPS GET with a 49K request header

skip test 410 for mesalink in the CI as it otherwise hangs "forever"

lib: pass in 'struct Curl_easy *' to most functions

... in most cases instead of 'struct connectdata *' but in some cases in
addition to.

- We mostly operate on transfers and no

lib: pass in 'struct Curl_easy *' to most functions

... in most cases instead of 'struct connectdata *' but in some cases in
addition to.

- We mostly operate on transfers and not connections.

- We need the transfer handle to log, store data and more. Everything in
libcurl is driven by a transfer (the CURL * in the public API).

- This work clarifies and separates the transfers from the connections
better.

- We should avoid "conn->data". Since individual connections can be used
by many transfers when multiplexing, making sure that conn->data
points to the current and correct transfer at all times is difficult
and has been notoriously error-prone over the years. The goal is to
ultimately remove the conn->data pointer for this reason.

Closes #6425

show more ...

docs: fix typos in NEW-PROTOCOL.md

This fixes a misspelled "it" and a grammatically wrong "-ing" suffix.

Closes #6471

RELEASE-NOTES: synced

cmake: expose CURL_DISABLE_OPENSSL_AUTO_LOAD_CONFIG

This does for cmake builds what --disable-openssl-auto-load-config
does for autoconf builds.

Closes https://github.com/curl/c

cmake: expose CURL_DISABLE_OPENSSL_AUTO_LOAD_CONFIG

This does for cmake builds what --disable-openssl-auto-load-config
does for autoconf builds.

Closes https://github.com/curl/curl/pull/6435

show more ...

test1918: verify curl_easy_option_by_name() and curl_easy_option_by_id()

... and as a practical side-effect, make sure that the
Curl_easyopts_check() function is asserted in debug builds

test1918: verify curl_easy_option_by_name() and curl_easy_option_by_id()

... and as a practical side-effect, make sure that the
Curl_easyopts_check() function is asserted in debug builds, which we
want to detect mismatches between the options list in easyoptions.c and
the options in curl.h

Found-by: Gisle Vanem
Bug: https://github.com/curl/curl/commit/08e8455dddc5e48e58a12ade3815c01ae3da3b64#commitcomment-45991815

Closes #6461

show more ...

easyoptions: add the missing AWS_SIGV4

Follow-up from AWS_SIGV4

schannel_verify: fix safefree call typo

Follow-up from e87ad71d1ba00519

Closes #6459

mime: make sure setting MIMEPOST to NULL resets properly

... so that a function can first use MIMEPOST and then set it to NULL to
reset it back to a blank POST.

Added test 584 t

mime: make sure setting MIMEPOST to NULL resets properly

... so that a function can first use MIMEPOST and then set it to NULL to
reset it back to a blank POST.

Added test 584 to verify the fix.

Reported-by: Christoph M. Becker

Fixes #6455
Closes #6456

show more ...

multi: set the PRETRANSFER time-stamp when we switch to PERFORM

... instead of at end of the DO state. This makes the timer more
accurate for the protocols that use the DOING state (such

multi: set the PRETRANSFER time-stamp when we switch to PERFORM

... instead of at end of the DO state. This makes the timer more
accurate for the protocols that use the DOING state (such as FTP), and
simplifies how the function (now called init_perform) is called.

The timer will then include the entire procedure up to PERFORM -
including all instructions for getting the transfer started.

Closes #6454

show more ...

CURLINFO_PRETRANSFER_TIME.3: clarify

... the timer *does* include the instructions for getting the remote
file.

Ref: #6452
Closes #6453

schannel: plug a memory-leak

... when built without -DUNICODE.

Closes #6457

gitattributes: Set batch files to CRLF line endings on checkout

If a batch file is run without CRLF line endings (ie LF-only) then
arbitrary behavior may occur. I consider that a bug in

gitattributes: Set batch files to CRLF line endings on checkout

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

show more ...

tool_operate: spellfix a comment

ROADMAP: refreshed

o removed HSTS - already implemented
o added HTTPS RR records
o mention HTTP/3 completion

http_chunks: remove Curl_ prefix from static functions

transfer: remove Curl_ prefix from static functions

tftp: remove Curl_ prefix from static functions

multi: remove Curl_ prefix from static functions

ldap: remove Curl_ prefix from static functions

doh: remove Curl_ prefix from static functions

asyn-ares: remove Curl_ prefix from static functions

vtls: remove Curl_ prefix from static functions

bearssl: remove Curl_ prefix from static functions