← Commit list

3eb57d6ba7

Daniel Stenberg

2025-01-02

SUCCESS Duration: 82s

Subject

docs: use lowercase curl and libcurl

Binary

Download Binary (866 KB)

Architecture & Compiler Flags

Architecture: x86_64-linux-gnu Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04.3) 11.4.0

—

Build Log

$ git checkout -f 3eb57d6ba74507df4a597f0a0c775a0eff66ba59
Previous HEAD position was d984209e59 smb: fix compiler warning
HEAD is now at 3eb57d6ba7 docs: use lowercase curl and libcurl

$ git clean -fdx
Removing Makefile
Removing Makefile.in
Removing aclocal.m4
Removing autom4te.cache/
Removing buildinfo.txt
Removing compile
Removing config.guess
Removing config.log
Removing config.status
Removing config.sub
Removing configure
Removing curl-config
Removing depcomp
Removing docs/Makefile
Removing docs/Makefile.in
Removing docs/cmdline-opts/Makefile
Removing docs/cmdline-opts/Makefile.in
Removing docs/examples/.deps/
Removing docs/examples/Makefile
Removing docs/examples/Makefile.in
Removing docs/libcurl/Makefile
Removing docs/libcurl/Makefile.in
Removing docs/libcurl/opts/Makefile
Removing docs/libcurl/opts/Makefile.in
Removing include/Makefile
Removing include/Makefile.in
Removing include/curl/Makefile
Removing include/curl/Makefile.in
Removing install-sh
Removing lib/.deps/
Removing lib/.dirstamp
Removing lib/.libs/
Removing lib/Makefile
Removing lib/Makefile.in
Removing lib/base64.o
Removing lib/curl_config.h
Removing lib/curl_config.h.in
Removing lib/curl_multibyte.o
Removing lib/dynbuf.o
Removing lib/libcurl.la
Removing lib/libcurl.vers
Removing lib/libcurl_la-altsvc.lo
Removing lib/libcurl_la-altsvc.o
Removing lib/libcurl_la-amigaos.lo
Removing lib/libcurl_la-amigaos.o
Removing lib/libcurl_la-asyn-ares.lo
Removing lib/libcurl_la-asyn-ares.o
Removing lib/libcurl_la-asyn-thread.lo
Removing lib/libcurl_la-asyn-thread.o
Removing lib/libcurl_la-base64.lo
Removing lib/libcurl_la-base64.o
Removing lib/libcurl_la-bufq.lo
Removing lib/libcurl_la-bufq.o
Removing lib/libcurl_la-bufref.lo
Removing lib/libcurl_la-bufref.o
Removing lib/libcurl_la-cf-h1-proxy.lo
Removing lib/libcurl_la-cf-h1-proxy.o
Removing lib/libcurl_la-cf-h2-proxy.lo
Removing lib/libcurl_la-cf-h2-proxy.o
Removing lib/libcurl_la-cf-haproxy.lo
Removing lib/libcurl_la-cf-haproxy.o
Removing lib/libcurl_la-cf-https-connect.lo
Removing lib/libcurl_la-cf-https-connect.o
Removing lib/libcurl_la-cf-socket.lo
Removing lib/libcurl_la-cf-socket.o
Removing lib/libcurl_la-cfilters.lo
Removing lib/libcurl_la-cfilters.o
Removing lib/libcurl_la-conncache.lo
Removing lib/libcurl_la-conncache.o
Removing lib/libcurl_la-connect.lo
Removing lib/libcurl_la-connect.o
Removing lib/libcurl_la-content_encoding.lo
Removing lib/libcurl_la-content_encoding.o
Removing lib/libcurl_la-cookie.lo
Removing lib/libcurl_la-cookie.o
Removing lib/libcurl_la-curl_addrinfo.lo
Removing lib/libcurl_la-curl_addrinfo.o
Removing lib/libcurl_la-curl_des.lo
Removing lib/libcurl_la-curl_des.o
Removing lib/libcurl_la-curl_endian.lo
Removing lib/libcurl_la-curl_endian.o
Removing lib/libcurl_la-curl_fnmatch.lo
Removing lib/libcurl_la-curl_fnmatch.o
Removing lib/libcurl_la-curl_get_line.lo
Removing lib/libcurl_la-curl_get_line.o
Removing lib/libcurl_la-curl_gethostname.lo
Removing lib/libcurl_la-curl_gethostname.o
Removing lib/libcurl_la-curl_gssapi.lo
Removing lib/libcurl_la-curl_gssapi.o
Removing lib/libcurl_la-curl_memrchr.lo
Removing lib/libcurl_la-curl_memrchr.o
Removing lib/libcurl_la-curl_multibyte.lo
Removing lib/libcurl_la-curl_multibyte.o
Removing lib/libcurl_la-curl_ntlm_core.lo
Removing lib/libcurl_la-curl_ntlm_core.o
Removing lib/libcurl_la-curl_range.lo
Removing lib/libcurl_la-curl_range.o
Removing lib/libcurl_la-curl_rtmp.lo
Removing lib/libcurl_la-curl_rtmp.o
Removing lib/libcurl_la-curl_sasl.lo
Removing lib/libcurl_la-curl_sasl.o
Removing lib/libcurl_la-curl_sha512_256.lo
Removing lib/libcurl_la-curl_sha512_256.o
Removing lib/libcurl_la-curl_sspi.lo
Removing lib/libcurl_la-curl_sspi.o
Removing lib/libcurl_la-curl_threads.lo
Removing lib/libcurl_la-curl_threads.o
Removing lib/libcurl_la-curl_trc.lo
Removing lib/libcurl_la-curl_trc.o
Removing lib/libcurl_la-cw-out.lo
Removing lib/libcurl_la-cw-out.o
Removing lib/libcurl_la-dict.lo
Removing lib/libcurl_la-dict.o
Removing lib/libcurl_la-dllmain.lo
Removing lib/libcurl_la-dllmain.o
Removing lib/libcurl_la-doh.lo
Removing lib/libcurl_la-doh.o
Removing lib/libcurl_la-dynbuf.lo
Removing lib/libcurl_la-dynbuf.o
Removing lib/libcurl_la-dynhds.lo
Removing lib/libcurl_la-dynhds.o
Removing lib/libcurl_la-easy.lo
Removing lib/libcurl_la-easy.o
Removing lib/libcurl_la-easygetopt.lo
Removing lib/libcurl_la-easygetopt.o
Removing lib/libcurl_la-easyoptions.lo
Removing lib/libcurl_la-easyoptions.o
Removing lib/libcurl_la-escape.lo
Removing lib/libcurl_la-escape.o
Removing lib/libcurl_la-file.lo
Removing lib/libcurl_la-file.o
Removing lib/libcurl_la-fileinfo.lo
Removing lib/libcurl_la-fileinfo.o
Removing lib/libcurl_la-fopen.lo
Removing lib/libcurl_la-fopen.o
Removing lib/libcurl_la-formdata.lo
Removing lib/libcurl_la-formdata.o
Removing lib/libcurl_la-ftp.lo
Removing lib/libcurl_la-ftp.o
Removing lib/libcurl_la-ftplistparser.lo
Removing lib/libcurl_la-ftplistparser.o
Removing lib/libcurl_la-getenv.lo
Removing lib/libcurl_la-getenv.o
Removing lib/libcurl_la-getinfo.lo
Removing lib/libcurl_la-getinfo.o
Removing lib/libcurl_la-gopher.lo
Removing lib/libcurl_la-gopher.o
Removing lib/libcurl_la-hash.lo
Removing lib/libcurl_la-hash.o
Removing lib/libcurl_la-headers.lo
Removing lib/libcurl_la-headers.o
Removing lib/libcurl_la-hmac.lo
Removing lib/libcurl_la-hmac.o
Removing lib/libcurl_la-hostasyn.lo
Removing lib/libcurl_la-hostasyn.o
Removing lib/libcurl_la-hostip.lo
Removing lib/libcurl_la-hostip.o
Removing lib/libcurl_la-hostip4.lo
Removing lib/libcurl_la-hostip4.o
Removing lib/libcurl_la-hostip6.lo
Removing lib/libcurl_la-hostip6.o
Removing lib/libcurl_la-hostsyn.lo
Removing lib/libcurl_la-hostsyn.o
Removing lib/libcurl_la-hsts.lo
Removing lib/libcurl_la-hsts.o
Removing lib/libcurl_la-http.lo
Removing lib/libcurl_la-http.o
Removing lib/libcurl_la-http1.lo
Removing lib/libcurl_la-http1.o
Removing lib/libcurl_la-http2.lo
Removing lib/libcurl_la-http2.o
Removing lib/libcurl_la-http_aws_sigv4.lo
Removing lib/libcurl_la-http_aws_sigv4.o
Removing lib/libcurl_la-http_chunks.lo
Removing lib/libcurl_la-http_chunks.o
Removing lib/libcurl_la-http_digest.lo
Removing lib/libcurl_la-http_digest.o
Removing lib/libcurl_la-http_negotiate.lo
Removing lib/libcurl_la-http_negotiate.o
Removing lib/libcurl_la-http_ntlm.lo
Removing lib/libcurl_la-http_ntlm.o
Removing lib/libcurl_la-http_proxy.lo
Removing lib/libcurl_la-http_proxy.o
Removing lib/libcurl_la-idn.lo
Removing lib/libcurl_la-idn.o
Removing lib/libcurl_la-if2ip.lo
Removing lib/libcurl_la-if2ip.o
Removing lib/libcurl_la-imap.lo
Removing lib/libcurl_la-imap.o
Removing lib/libcurl_la-inet_ntop.lo
Removing lib/libcurl_la-inet_ntop.o
Removing lib/libcurl_la-inet_pton.lo
Removing lib/libcurl_la-inet_pton.o
Removing lib/libcurl_la-krb5.lo
Removing lib/libcurl_la-krb5.o
Removing lib/libcurl_la-ldap.lo
Removing lib/libcurl_la-ldap.o
Removing lib/libcurl_la-llist.lo
Removing lib/libcurl_la-llist.o
Removing lib/libcurl_la-macos.lo
Removing lib/libcurl_la-macos.o
Removing lib/libcurl_la-md4.lo
Removing lib/libcurl_la-md4.o
Removing lib/libcurl_la-md5.lo
Removing lib/libcurl_la-md5.o
Removing lib/libcurl_la-memdebug.lo
Removing lib/libcurl_la-memdebug.o
Removing lib/libcurl_la-mime.lo
Removing lib/libcurl_la-mime.o
Removing lib/libcurl_la-mprintf.lo
Removing lib/libcurl_la-mprintf.o
Removing lib/libcurl_la-mqtt.lo
Removing lib/libcurl_la-mqtt.o
Removing lib/libcurl_la-multi.lo
Removing lib/libcurl_la-multi.o
Removing lib/libcurl_la-netrc.lo
Removing lib/libcurl_la-netrc.o
Removing lib/libcurl_la-nonblock.lo
Removing lib/libcurl_la-nonblock.o
Removing lib/libcurl_la-noproxy.lo
Removing lib/libcurl_la-noproxy.o
Removing lib/libcurl_la-openldap.lo
Removing lib/libcurl_la-openldap.o
Removing lib/libcurl_la-parsedate.lo
Removing lib/libcurl_la-parsedate.o
Removing lib/libcurl_la-pingpong.lo
Removing lib/libcurl_la-pingpong.o
Removing lib/libcurl_la-pop3.lo
Removing lib/libcurl_la-pop3.o
Removing lib/libcurl_la-progress.lo
Removing lib/libcurl_la-progress.o
Removing lib/libcurl_la-psl.lo
Removing lib/libcurl_la-psl.o
Removing lib/libcurl_la-rand.lo
Removing lib/libcurl_la-rand.o
Removing lib/libcurl_la-rename.lo
Removing lib/libcurl_la-rename.o
Removing lib/libcurl_la-request.lo
Removing lib/libcurl_la-request.o
Removing lib/libcurl_la-rtsp.lo
Removing lib/libcurl_la-rtsp.o
Removing lib/libcurl_la-select.lo
Removing lib/libcurl_la-select.o
Removing lib/libcurl_la-sendf.lo
Removing lib/libcurl_la-sendf.o
Removing lib/libcurl_la-setopt.lo
Removing lib/libcurl_la-setopt.o
Removing lib/libcurl_la-sha256.lo
Removing lib/libcurl_la-sha256.o
Removing lib/libcurl_la-share.lo
Removing lib/libcurl_la-share.o
Removing lib/libcurl_la-slist.lo
Removing lib/libcurl_la-slist.o
Removing lib/libcurl_la-smb.lo
Removing lib/libcurl_la-smb.o
Removing lib/libcurl_la-smtp.lo
Removing lib/libcurl_la-smtp.o
Removing lib/libcurl_la-socketpair.lo
Removing lib/libcurl_la-socketpair.o
Removing lib/libcurl_la-socks.lo
Removing lib/libcurl_la-socks.o
Removing lib/libcurl_la-socks_gssapi.lo
Removing lib/libcurl_la-socks_gssapi.o
Removing lib/libcurl_la-socks_sspi.lo
Removing lib/libcurl_la-socks_sspi.o
Removing lib/libcurl_la-speedcheck.lo
Removing lib/libcurl_la-speedcheck.o
Removing lib/libcurl_la-splay.lo
Removing lib/libcurl_la-splay.o
Removing lib/libcurl_la-strcase.lo
Removing lib/libcurl_la-strcase.o
Removing lib/libcurl_la-strdup.lo
Removing lib/libcurl_la-strdup.o
Removing lib/libcurl_la-strerror.lo
Removing lib/libcurl_la-strerror.o
Removing lib/libcurl_la-strparse.lo
Removing lib/libcurl_la-strparse.o
Removing lib/libcurl_la-strtok.lo
Removing lib/libcurl_la-strtok.o
Removing lib/libcurl_la-strtoofft.lo
Removing lib/libcurl_la-strtoofft.o
Removing lib/libcurl_la-system_win32.lo
Removing lib/libcurl_la-system_win32.o
Removing lib/libcurl_la-telnet.lo
Removing lib/libcurl_la-telnet.o
Removing lib/libcurl_la-tftp.lo
Removing lib/libcurl_la-tftp.o
Removing lib/libcurl_la-timediff.lo
Removing lib/libcurl_la-timediff.o
Removing lib/libcurl_la-timeval.lo
Removing lib/libcurl_la-timeval.o
Removing lib/libcurl_la-transfer.lo
Removing lib/libcurl_la-transfer.o
Removing lib/libcurl_la-url.lo
Removing lib/libcurl_la-url.o
Removing lib/libcurl_la-urlapi.lo
Removing lib/libcurl_la-urlapi.o
Removing lib/libcurl_la-version.lo
Removing lib/libcurl_la-version.o
Removing lib/libcurl_la-version_win32.lo
Removing lib/libcurl_la-version_win32.o
Removing lib/libcurl_la-warnless.lo
Removing lib/libcurl_la-warnless.o
Removing lib/libcurl_la-ws.lo
Removing lib/libcurl_la-ws.o
Removing lib/nonblock.o
Removing lib/stamp-h1
Removing lib/strtoofft.o
Removing lib/timediff.o
Removing lib/vauth/.deps/
Removing lib/vauth/.dirstamp
Removing lib/vauth/libcurl_la-cleartext.lo
Removing lib/vauth/libcurl_la-cleartext.o
Removing lib/vauth/libcurl_la-cram.lo
Removing lib/vauth/libcurl_la-cram.o
Removing lib/vauth/libcurl_la-digest.lo
Removing lib/vauth/libcurl_la-digest.o
Removing lib/vauth/libcurl_la-digest_sspi.lo
Removing lib/vauth/libcurl_la-digest_sspi.o
Removing lib/vauth/libcurl_la-gsasl.lo
Removing lib/vauth/libcurl_la-gsasl.o
Removing lib/vauth/libcurl_la-krb5_gssapi.lo
Removing lib/vauth/libcurl_la-krb5_gssapi.o
Removing lib/vauth/libcurl_la-krb5_sspi.lo
Removing lib/vauth/libcurl_la-krb5_sspi.o
Removing lib/vauth/libcurl_la-ntlm.lo
Removing lib/vauth/libcurl_la-ntlm.o
Removing lib/vauth/libcurl_la-ntlm_sspi.lo
Removing lib/vauth/libcurl_la-ntlm_sspi.o
Removing lib/vauth/libcurl_la-oauth2.lo
Removing lib/vauth/libcurl_la-oauth2.o
Removing lib/vauth/libcurl_la-spnego_gssapi.lo
Removing lib/vauth/libcurl_la-spnego_gssapi.o
Removing lib/vauth/libcurl_la-spnego_sspi.lo
Removing lib/vauth/libcurl_la-spnego_sspi.o
Removing lib/vauth/libcurl_la-vauth.lo
Removing lib/vauth/libcurl_la-vauth.o
Removing lib/version_win32.o
Removing lib/vquic/.deps/
Removing lib/vquic/.dirstamp
Removing lib/vquic/libcurl_la-curl_msh3.lo
Removing lib/vquic/libcurl_la-curl_msh3.o
Removing lib/vquic/libcurl_la-curl_ngtcp2.lo
Removing lib/vquic/libcurl_la-curl_ngtcp2.o
Removing lib/vquic/libcurl_la-curl_osslq.lo
Removing lib/vquic/libcurl_la-curl_osslq.o
Removing lib/vquic/libcurl_la-curl_quiche.lo
Removing lib/vquic/libcurl_la-curl_quiche.o
Removing lib/vquic/libcurl_la-vquic-tls.lo
Removing lib/vquic/libcurl_la-vquic-tls.o
Removing lib/vquic/libcurl_la-vquic.lo
Removing lib/vquic/libcurl_la-vquic.o
Removing lib/vssh/.deps/
Removing lib/vssh/.dirstamp
Removing lib/vssh/libcurl_la-curl_path.lo
Removing lib/vssh/libcurl_la-curl_path.o
Removing lib/vssh/libcurl_la-libssh.lo
Removing lib/vssh/libcurl_la-libssh.o
Removing lib/vssh/libcurl_la-libssh2.lo
Removing lib/vssh/libcurl_la-libssh2.o
Removing lib/vssh/libcurl_la-wolfssh.lo
Removing lib/vssh/libcurl_la-wolfssh.o
Removing lib/vtls/.deps/
Removing lib/vtls/.dirstamp
Removing lib/vtls/libcurl_la-bearssl.lo
Removing lib/vtls/libcurl_la-bearssl.o
Removing lib/vtls/libcurl_la-cipher_suite.lo
Removing lib/vtls/libcurl_la-cipher_suite.o
Removing lib/vtls/libcurl_la-gtls.lo
Removing lib/vtls/libcurl_la-gtls.o
Removing lib/vtls/libcurl_la-hostcheck.lo
Removing lib/vtls/libcurl_la-hostcheck.o
Removing lib/vtls/libcurl_la-keylog.lo
Removing lib/vtls/libcurl_la-keylog.o
Removing lib/vtls/libcurl_la-mbedtls.lo
Removing lib/vtls/libcurl_la-mbedtls.o
Removing lib/vtls/libcurl_la-mbedtls_threadlock.lo
Removing lib/vtls/libcurl_la-mbedtls_threadlock.o
Removing lib/vtls/libcurl_la-openssl.lo
Removing lib/vtls/libcurl_la-openssl.o
Removing lib/vtls/libcurl_la-rustls.lo
Removing lib/vtls/libcurl_la-rustls.o
Removing lib/vtls/libcurl_la-schannel.lo
Removing lib/vtls/libcurl_la-schannel.o
Removing lib/vtls/libcurl_la-schannel_verify.lo
Removing lib/vtls/libcurl_la-schannel_verify.o
Removing lib/vtls/libcurl_la-sectransp.lo
Removing lib/vtls/libcurl_la-sectransp.o
Removing lib/vtls/libcurl_la-vtls.lo
Removing lib/vtls/libcurl_la-vtls.o
Removing lib/vtls/libcurl_la-vtls_scache.lo
Removing lib/vtls/libcurl_la-vtls_scache.o
Removing lib/vtls/libcurl_la-wolfssl.lo
Removing lib/vtls/libcurl_la-wolfssl.o
Removing lib/vtls/libcurl_la-x509asn1.lo
Removing lib/vtls/libcurl_la-x509asn1.o
Removing lib/warnless.o
Removing libcurl.pc
Removing libtool
Removing ltmain.sh
Removing m4/libtool.m4
Removing m4/ltoptions.m4
Removing m4/ltsugar.m4
Removing m4/ltversion.m4
Removing m4/lt~obsolete.m4
Removing missing
Removing packages/Makefile
Removing packages/Makefile.in
Removing packages/vms/Makefile
Removing packages/vms/Makefile.in
Removing scripts/Makefile
Removing scripts/Makefile.in
Removing src/.deps/
Removing src/.libs/
Removing src/Makefile
Removing src/Makefile.in
Removing src/curl
Removing src/slist_wc.o
Removing src/terminal.o
Removing src/tool_bname.o
Removing src/tool_ca_embed.c
Removing src/tool_ca_embed.o
Removing src/tool_cb_dbg.o
Removing src/tool_cb_hdr.o
Removing src/tool_cb_prg.o
Removing src/tool_cb_rea.o
Removing src/tool_cb_see.o
Removing src/tool_cb_soc.o
Removing src/tool_cb_wrt.o
Removing src/tool_cfgable.o
Removing src/tool_dirhie.o
Removing src/tool_doswin.o
Removing src/tool_easysrc.o
Removing src/tool_filetime.o
Removing src/tool_findfile.o
Removing src/tool_formparse.o
Removing src/tool_getparam.o
Removing src/tool_getpass.o
Removing src/tool_help.o
Removing src/tool_helpers.o
Removing src/tool_hugehelp.c
Removing src/tool_hugehelp.o
Removing src/tool_ipfs.o
Removing src/tool_libinfo.o
Removing src/tool_listhelp.o
Removing src/tool_main.o
Removing src/tool_msgs.o
Removing src/tool_operate.o
Removing src/tool_operhlp.o
Removing src/tool_paramhlp.o
Removing src/tool_parsecfg.o
Removing src/tool_progress.o
Removing src/tool_setopt.o
Removing src/tool_sleep.o
Removing src/tool_stderr.o
Removing src/tool_strdup.o
Removing src/tool_urlglob.o
Removing src/tool_util.o
Removing src/tool_vms.o
Removing src/tool_writeout.o
Removing src/tool_writeout_json.o
Removing src/tool_xattr.o
Removing src/var.o
Removing tests/Makefile
Removing tests/Makefile.in
Removing tests/certs/Makefile
Removing tests/certs/Makefile.in
Removing tests/certs/scripts/Makefile
Removing tests/certs/scripts/Makefile.in
Removing tests/config
Removing tests/configurehelp.pm
Removing tests/data/Makefile
Removing tests/data/Makefile.in
Removing tests/http/Makefile
Removing tests/http/Makefile.in
Removing tests/http/clients/.deps/
Removing tests/http/clients/Makefile
Removing tests/http/clients/Makefile.in
Removing tests/http/config.ini
Removing tests/libtest/.deps/
Removing tests/libtest/Makefile
Removing tests/libtest/Makefile.in
Removing tests/server/.deps/
Removing tests/server/Makefile
Removing tests/server/Makefile.in
Removing tests/unit/.deps/
Removing tests/unit/Makefile
Removing tests/unit/Makefile.in

$ autoreconf -fi
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Remember to add 'LT_INIT' to configure.ac.
configure.ac:125: installing './compile'
configure.ac:429: installing './config.guess'
configure.ac:429: installing './config.sub'
configure.ac:125: installing './install-sh'
configure.ac:131: installing './missing'
docs/examples/Makefile.am: installing './depcomp'

$ bash -c find . -name config.guess -exec cp /usr/share/misc/config.guess {} \;

$ bash -c find . -name config.sub -exec cp /usr/share/misc/config.sub {} \;

$ chmod +x configure

$ ./configure --disable-shared --without-ssl --disable-docs
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking whether to enable debug build options... no
checking whether to enable compiler optimizer... (assumed) yes
checking whether to enable strict compiler warnings... no
checking whether to enable compiler warnings as errors... no
checking whether to enable curl debug memory tracking... no
checking whether to enable hiding of library internal symbols... yes
checking whether to enable c-ares for DNS lookups... no
checking whether to disable dependency on -lrt... (assumed no)
checking whether to enable HTTPSRR support... no
checking whether to enable ECH support... no
checking for path separator... :
checking for sed... /usr/bin/sed
checking for grep... /usr/bin/grep
checking that grep -E works... yes
checking for ar... /usr/bin/ar
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... ccache gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether ccache gcc accepts -g... yes
checking for ccache gcc option to enable C11 features... none needed
checking whether ccache gcc understands -c and -o together... yes
checking how to run the C preprocessor... ccache gcc -E
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for stdatomic.h... yes
checking if _Atomic is available... yes
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for code coverage support... no
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of ccache gcc... gcc3
checking curl version... 8.12.0-DEV
checking for httpd... no
checking for apache2... no
checking for apachectl... no
checking for apxs... no
configure: httpd/apache2 not in PATH, http tests disabled
configure: apxs not in PATH, http tests disabled
checking for nghttpx... no
checking for caddy... /usr/bin/caddy
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking if OS is AIX (to define _ALL_SOURCE)... no
checking if _THREAD_SAFE is already defined... no
checking if _THREAD_SAFE is actually needed... no
checking if _THREAD_SAFE is onwards defined... no
checking if _REENTRANT is already defined... no
checking if _REENTRANT is actually needed... no
checking if _REENTRANT is onwards defined... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by ccache gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from ccache gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if ccache gcc supports -fno-rtti -fno-exceptions... no
checking for ccache gcc option to produce PIC... -fPIC -DPIC
checking if ccache gcc PIC flag -fPIC -DPIC works... yes
checking if ccache gcc static flag -static works... yes
checking if ccache gcc supports -c -o file.o... yes
checking if ccache gcc supports -c -o file.o... (cached) yes
checking whether the ccache gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking whether to build shared libraries with -version-info... yes
checking whether to build shared libraries with -no-undefined... no
checking whether to build shared libraries with -mimpure-text... no
checking whether to build shared libraries with PIC... yes
checking whether to build static libraries with PIC... yes
checking whether to build shared libraries only... no
checking whether to build static libraries only... yes
checking for windres... no
checking if cpp -P is needed... yes
checking if cpp -P works... yes
checking if compiler is DEC/Compaq/HP C... no
checking if compiler is HP-UX C... no
checking if compiler is IBM C... no
checking if compiler is Intel C... no
checking if compiler is clang... no
checking if compiler is GNU C... yes
checking compiler version... gcc '1100' (raw: '11')
checking if compiler is SunPro C... no
checking if compiler is Tiny C... no
checking whether build target is a native Windows one... no
checking if compiler accepts some basic options... yes
configure: compiler options added: -Werror-implicit-function-declaration
checking if compiler optimizer assumed setting might be used... yes
checking if compiler accepts optimizer enabling options... yes
configure: compiler options added: -O2
checking if compiler accepts strict warning options... yes
configure: compiler options added: -Wno-system-headers
checking if compiler halts on compilation errors... yes
checking if compiler halts on negative sized arrays... yes
checking if compiler halts on function prototype mismatch... yes
checking if compiler supports hiding library internal symbols... yes
checking whether build target supports Win32 file API... no
checking whether build target supports Win32 crypto API... no
checking for good-to-use Darwin CFLAGS... no
checking whether to build libcurl and curl in "unity" mode... no
checking whether to build tests into single-binary bundles... no
checking whether to support http... yes
checking whether to support ftp... yes
checking whether to support file... yes
checking whether to support IPFS... yes
checking whether to support ldap... yes
checking whether to support ldaps... yes
checking whether to support rtsp... yes
checking whether to support proxies... yes
checking whether to support dict... yes
checking whether to support telnet... yes
checking whether to support tftp... yes
checking whether to support pop3... yes
checking whether to support imap... yes
checking whether to support smb... yes
checking whether to support smtp... yes
checking whether to support gopher... yes
checking whether to support mqtt... no
checking whether to provide built-in manual... yes
checking whether to build documentation... no
checking whether to enable generation of C code... yes
checking whether to use libgcc... no
checking if X/Open network library is required... no
checking for gethostbyname... yes
checking whether build target is a native Windows one... (cached) no
checking for proto/bsdsocket.h... no
checking for connect in libraries... yes
checking for sys/types.h... (cached) yes
checking for sys/time.h... yes
checking for monotonic clock_gettime... yes
checking for clock_gettime in libraries... no additional lib required
checking if monotonic clock_gettime works... yes
checking for sys/types.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for raw monotonic clock_gettime... yes
checking for pkg-config... /usr/bin/pkg-config
checking for zlib options with pkg-config... found
checking for zlib.h... yes
configure: found both libz and libz.h header
checking for BrotliDecoderDecompress in -lbrotlidec... no
checking for brotli/decode.h... no
checking for ZSTD_createDStream in -lzstd... no
checking for zstd.h... no
checking for lber.h... no
checking for ldap.h... no
checking for ldap_ssl.h... no
checking for LDAP libraries... cannot find LDAP libraries
checking whether to enable IPv6... yes
checking if struct sockaddr_in6 has sin6_scope_id member... yes
checking if argv can be written to... yes
checking if GSS-API support is requested... no
checking whether to enable Windows native SSL/TLS... no
checking whether to enable Secure Transport... no
checking whether to enable Amiga native SSL/TLS (AmiSSL v5)... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for libpsl options with pkg-config... found
checking for psl_builtin in -lpsl... yes
checking for libpsl.h... yes
checking for library containing gsasl_init... no
checking for RTMP_Init in -lrtmp... no
checking whether versioned symbols are wanted... no
checking whether to build with libidn2... (assumed) yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for libidn2 options with pkg-config... no
configure: IDN_LIBS: "-lidn2"
configure: IDN_LDFLAGS: ""
configure: IDN_CPPFLAGS: ""
configure: IDN_DIR: ""
checking if idn2_lookup_ul can be linked... no
checking for idn2.h... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for libnghttp2 options with pkg-config... no
checking for nghttp2_session_get_stream_local_window_size in -lnghttp2... no
checking for sys/types.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking for arpa/inet.h... yes
checking for net/if.h... yes
checking for netinet/in.h... yes
checking for netinet/in6.h... no
checking for sys/un.h... yes
checking for linux/tcp.h... yes
checking for netinet/tcp.h... yes
checking for netinet/udp.h... yes
checking for netdb.h... yes
checking for sys/sockio.h... no
checking for sys/stat.h... (cached) yes
checking for sys/param.h... yes
checking for termios.h... yes
checking for termio.h... yes
checking for fcntl.h... yes
checking for io.h... no
checking for pwd.h... yes
checking for utime.h... yes
checking for sys/utime.h... no
checking for sys/poll.h... yes
checking for poll.h... yes
checking for sys/resource.h... yes
checking for libgen.h... yes
checking for locale.h... yes
checking for stdbool.h... yes
checking for sys/filio.h... no
checking for sys/eventfd.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for sys/types.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for struct timeval... yes
checking run-time libs availability... fine
checking size of size_t... 8
checking size of long... 8
checking size of int... 4
checking size of time_t... 8
checking size of off_t... 8
checking size of curl_off_t... 8
checking size of curl_socket_t... 4
checking for long long... yes
checking for ssize_t... yes
checking for bool... yes
checking for sa_family_t... yes
checking for suseconds_t... yes
checking if time_t is unsigned... no
checking for in_addr_t... yes
checking for struct sockaddr_storage... yes
checking for sys/select.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for select... yes
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for recv... yes
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for send... yes
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for sys/types.h... (cached) yes
checking for unistd.h... (cached) yes
checking if alarm can be linked... yes
checking if alarm is prototyped... yes
checking if alarm is compilable... yes
checking if alarm usage allowed... yes
checking if alarm might be used... yes
checking for sys/types.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for libgen.h... (cached) yes
checking if basename can be linked... yes
checking if basename is prototyped... yes
checking if basename is compilable... yes
checking if basename usage allowed... yes
checking if basename might be used... yes
checking if closesocket can be linked... no
checking if closesocket might be used... no
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking if CloseSocket can be linked... no
checking if CloseSocket might be used... no
checking for sys/types.h... (cached) yes
checking for unistd.h... (cached) yes
checking for fcntl.h... (cached) yes
checking if fcntl can be linked... yes
checking if fcntl is prototyped... yes
checking if fcntl is compilable... yes
checking if fcntl usage allowed... yes
checking if fcntl might be used... yes
checking if fcntl O_NONBLOCK is compilable... yes
checking if fcntl O_NONBLOCK usage allowed... yes
checking if fcntl O_NONBLOCK might be used... yes
checking whether build target is a native Windows one... (cached) no
checking for sys/types.h... (cached) yes
checking for netdb.h... (cached) yes
checking if freeaddrinfo can be linked... yes
checking if freeaddrinfo is prototyped... yes
checking if freeaddrinfo is compilable... yes
checking if freeaddrinfo usage allowed... yes
checking if freeaddrinfo might be used... yes
checking for sys/types.h... (cached) yes
checking for sys/xattr.h... yes
checking if fsetxattr can be linked... yes
checking if fsetxattr is prototyped... yes
checking if fsetxattr takes 5 args.... yes
checking if fsetxattr is compilable... yes
checking if fsetxattr usage allowed... yes
checking if fsetxattr might be used... yes
checking if ftruncate can be linked... yes
checking if ftruncate is prototyped... yes
checking if ftruncate is compilable... yes
checking if ftruncate usage allowed... yes
checking if ftruncate might be used... yes
checking for sys/types.h... (cached) yes
checking if getaddrinfo can be linked... yes
checking if getaddrinfo is prototyped... yes
checking if getaddrinfo is compilable... yes
checking if getaddrinfo seems to work... yes
checking if getaddrinfo usage allowed... yes
checking if getaddrinfo might be used... yes
checking if getaddrinfo is threadsafe... yes
checking if gethostbyname_r can be linked... yes
checking if gethostbyname_r is prototyped... yes
checking if gethostbyname_r takes 3 args.... no
checking if gethostbyname_r takes 5 args.... no
checking if gethostbyname_r takes 6 args.... yes
checking if gethostbyname_r is compilable... yes
checking if gethostbyname_r usage allowed... yes
checking if gethostbyname_r might be used... yes
checking if gethostname can be linked... yes
checking if gethostname is prototyped... yes
checking if gethostname is compilable... yes
checking for gethostname arg 2 data type... size_t
checking if gethostname usage allowed... yes
checking if gethostname might be used... yes
checking if getpeername can be linked... yes
checking if getpeername is prototyped... yes
checking if getpeername is compilable... yes
checking if getpeername usage allowed... yes
checking if getpeername might be used... yes
checking if getsockname can be linked... yes
checking if getsockname is prototyped... yes
checking if getsockname is compilable... yes
checking if getsockname usage allowed... yes
checking if getsockname might be used... yes
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for ifaddrs.h... yes
checking if getifaddrs can be linked... yes
checking if getifaddrs is prototyped... yes
checking if getifaddrs is compilable... yes
checking if getifaddrs seems to work... yes
checking if getifaddrs usage allowed... yes
checking if getifaddrs might be used... yes
checking for sys/types.h... (cached) yes
checking for sys/time.h... (cached) yes
checking if gmtime_r can be linked... yes
checking if gmtime_r is prototyped... yes
checking if gmtime_r is compilable... yes
checking if gmtime_r seems to work... yes
checking if gmtime_r usage allowed... yes
checking if gmtime_r might be used... yes
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for arpa/inet.h... (cached) yes
checking if inet_ntop can be linked... yes
checking if inet_ntop is prototyped... yes
checking if inet_ntop is compilable... yes
checking if inet_ntop seems to work... yes
checking if inet_ntop usage allowed... yes
checking if inet_ntop might be used... yes
checking if inet_pton can be linked... yes
checking if inet_pton is prototyped... yes
checking if inet_pton is compilable... yes
checking if inet_pton seems to work... yes
checking if inet_pton usage allowed... yes
checking if inet_pton might be used... yes
checking for sys/types.h... (cached) yes
checking for unistd.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for sys/ioctl.h... (cached) yes
checking for stropts.h... no
checking if ioctl can be linked... yes
checking if ioctl is prototyped... yes
checking if ioctl is compilable... yes
checking if ioctl usage allowed... yes
checking if ioctl might be used... yes
checking if ioctl FIONBIO is compilable... yes
checking if ioctl FIONBIO usage allowed... yes
checking if ioctl FIONBIO might be used... yes
checking if ioctl SIOCGIFADDR is compilable... yes
checking if ioctl SIOCGIFADDR usage allowed... yes
checking if ioctl SIOCGIFADDR might be used... yes
checking if ioctlsocket can be linked... no
checking if ioctlsocket might be used... no
checking if IoctlSocket can be linked... no
checking if IoctlSocket might be used... no
checking if memrchr can be linked... yes
checking if memrchr is prototyped... yes
checking if memrchr is compilable... yes
checking if memrchr usage allowed... yes
checking if memrchr might be used... yes
checking for sys/types.h... (cached) yes
checking if sigaction can be linked... yes
checking if sigaction is prototyped... yes
checking if sigaction is compilable... yes
checking if sigaction usage allowed... yes
checking if sigaction might be used... yes
checking if siginterrupt can be linked... yes
checking if siginterrupt is prototyped... yes
checking if siginterrupt is compilable... yes
checking if siginterrupt usage allowed... yes
checking if siginterrupt might be used... yes
checking if signal can be linked... yes
checking if signal is prototyped... yes
checking if signal is compilable... yes
checking if signal usage allowed... yes
checking if signal might be used... yes
checking for sys/types.h... (cached) yes
checking if sigsetjmp can be linked... no
checking if sigsetjmp seems a macro... yes
checking if sigsetjmp is compilable... yes
checking if sigsetjmp usage allowed... yes
checking if sigsetjmp might be used... yes
checking if socket can be linked... yes
checking if socket is prototyped... yes
checking if socket is compilable... yes
checking if socket usage allowed... yes
checking if socket might be used... yes
checking if socketpair can be linked... yes
checking if socketpair is prototyped... yes
checking if socketpair is compilable... yes
checking if socketpair usage allowed... yes
checking if socketpair might be used... yes
checking if strdup can be linked... yes
checking if strdup is prototyped... yes
checking if strdup is compilable... yes
checking if strdup usage allowed... yes
checking if strdup might be used... yes
checking if strerror_r can be linked... yes
checking if strerror_r is prototyped... yes
checking if strerror_r is compilable... yes
checking if strerror_r is glibc like... yes
checking if strerror_r seems to work... yes
checking if strerror_r usage allowed... yes
checking if strerror_r might be used... yes
checking if strtok_r can be linked... yes
checking if strtok_r is prototyped... yes
checking if strtok_r is compilable... yes
checking if strtok_r usage allowed... yes
checking if strtok_r might be used... yes
checking if strtoll can be linked... yes
checking if strtoll is prototyped... yes
checking if strtoll is compilable... yes
checking if strtoll usage allowed... yes
checking if strtoll might be used... yes
checking for eventfd... yes
checking for fnmatch... yes
checking for geteuid... yes
checking for getpass_r... no
checking for getppid... yes
checking for getpwuid... yes
checking for getpwuid_r... yes
checking for getrlimit... yes
checking for gettimeofday... yes
checking for if_nametoindex... yes
checking for mach_absolute_time... no
checking for pipe... yes
checking for poll... yes
checking for sched_yield... yes
checking for sendmsg... yes
checking for sendmmsg... yes
checking for setlocale... yes
checking for setmode... no
checking for setrlimit... yes
checking for snprintf... yes
checking for utime... yes
checking for utimes... yes
checking if strcasecmp can be linked... yes
checking if strcasecmp is prototyped... yes
checking if strcasecmp is compilable... yes
checking if strcasecmp usage allowed... yes
checking if strcasecmp might be used... yes
checking if strcmpi can be linked... no
checking if strcmpi might be used... no
checking if stricmp can be linked... no
checking if stricmp might be used... no
checking for arc4random... no
checking for fseeko... yes
checking for ccache gcc options needed to detect all undeclared functions... none needed
checking whether fseeko is declared... yes
checking how to set a socket into non-blocking mode... fcntl O_NONBLOCK
checking for perl... /usr/bin/perl
checking whether to enable the threaded resolver... yes
checking whether to link macOS CoreFoundation, CoreServices, and SystemConfiguration frameworks... no
checking whether to use POSIX threads for threaded resolver... auto
checking for pthread.h... yes
checking for pthread_create... yes
checking for dirent.h... yes
checking for opendir... yes
checking convert -I options to -isystem... yes
checking whether to enable verbose strings... yes
checking whether to enable SSPI support (Windows native builds only)... no
checking whether to enable basic authentication method... yes
checking whether to enable bearer authentication method... yes
checking whether to enable digest authentication method... yes
checking whether to enable kerberos authentication method... yes
checking whether to enable negotiate authentication method... yes
checking whether to enable aws sig methods... yes
checking whether to support NTLM... yes
checking whether to enable TLS-SRP authentication... yes
checking whether to enable Unix domain sockets... auto
checking for struct sockaddr_un.sun_path... yes
checking whether to support cookies... yes
checking whether to support socketpair... yes
checking whether to support HTTP authentication... yes
checking whether to support DoH... yes
checking whether to support the MIME API... yes
checking whether to support binding connections locally... yes
checking whether to support the form API... yes
checking whether to support date parsing... yes
checking whether to support netrc parsing... yes
checking whether to support progress-meter... yes
checking whether to support the SHA-512/256 hash algorithm... yes
checking whether to support DNS shuffling... yes
checking whether to support curl_easy_option*... yes
checking whether to support alt-svc... yes
checking whether to support headers-api... yes
configure: disables HSTS due to lack of SSL
checking whether to support WebSockets... yes
checking whether hiding of library internal symbols will actually happen... yes
checking if this build supports HTTPS-proxy... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating docs/examples/Makefile
config.status: creating docs/libcurl/Makefile
config.status: creating docs/libcurl/opts/Makefile
config.status: creating docs/cmdline-opts/Makefile
config.status: creating include/Makefile
config.status: creating include/curl/Makefile
config.status: creating src/Makefile
config.status: creating lib/Makefile
config.status: creating scripts/Makefile
config.status: creating lib/libcurl.vers
config.status: creating tests/Makefile
config.status: creating tests/config
config.status: creating tests/configurehelp.pm
config.status: creating tests/certs/Makefile
config.status: creating tests/certs/scripts/Makefile
config.status: creating tests/data/Makefile
config.status: creating tests/server/Makefile
config.status: creating tests/libtest/Makefile
config.status: creating tests/unit/Makefile
config.status: creating tests/http/config.ini
config.status: creating tests/http/Makefile
config.status: creating tests/http/clients/Makefile
config.status: creating packages/Makefile
config.status: creating packages/vms/Makefile
config.status: creating curl-config
config.status: creating libcurl.pc
config.status: creating lib/curl_config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: Configured to build curl/libcurl:

Host setup: x86_64-pc-linux-gnu
Install prefix: /usr/local
Compiler: ccache gcc
CFLAGS: -Werror-implicit-function-declaration -O2 -Wno-system-headers
CFLAGS extras:
CPPFLAGS: -D_GNU_SOURCE
LDFLAGS:
curl-config:
LIBS: -lpsl -lz

curl version: 8.12.0-DEV
SSL: no (--with-{openssl,gnutls,mbedtls,wolfssl,schannel,secure-transport,amissl,bearssl,rustls} )
SSH: no (--with-{libssh,libssh2})
zlib: enabled
brotli: no (--with-brotli)
zstd: no (--with-zstd)
GSS-API: no (--with-gssapi)
GSASL: no (libgsasl not found)
TLS-SRP: no (--enable-tls-srp)
resolver: POSIX threaded
IPv6: enabled
Unix sockets: enabled
IDN: no (--with-{libidn2,winidn})
Build docs: no
Build libcurl: Shared=no, Static=yes
Built-in manual: no (--enable-manual)
--libcurl option: enabled (--disable-libcurl-option)
Verbose errors: enabled (--disable-verbose)
Code coverage: disabled
SSPI: no (--enable-sspi)
ca cert bundle: no
ca cert path:
ca cert embed: no
ca fallback:
LDAP: no (--enable-ldap / --with-ldap-lib / --with-lber-lib)
LDAPS: no (--enable-ldaps)
IPFS/IPNS: enabled
RTSP: enabled
RTMP: no (--with-librtmp)
PSL: enabled
Alt-svc: enabled (--disable-alt-svc)
Headers API: enabled (--disable-headers-api)
HSTS: no (--enable-hsts)
HTTP1: enabled (internal)
HTTP2: no (--with-nghttp2)
HTTP3: no (--with-ngtcp2 --with-nghttp3, --with-quiche, --with-openssl-quic, --with-msh3)
ECH: no (--enable-ech)
Protocols: dict file ftp gopher http imap ipfs ipns mqtt pop3 rtsp smtp telnet tftp ws
Features: alt-svc AsynchDNS IPv6 Largefile libz PSL threadsafe UnixSockets

configure: WARNING: Cannot find libraries for LDAP support: LDAP disabled
configure: WARNING: libgsasl was not found
configure: WARNING: Cannot find libidn2

$ make -j3
Making all in lib
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/lib'
make all-am
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/lib'
CC libcurl_la-amigaos.lo
CC libcurl_la-altsvc.lo
CC libcurl_la-asyn-ares.lo
CC libcurl_la-asyn-thread.lo
CC libcurl_la-base64.lo
CC libcurl_la-bufq.lo
CC libcurl_la-bufref.lo
CC libcurl_la-cf-h1-proxy.lo
CC libcurl_la-cf-h2-proxy.lo
CC libcurl_la-cf-haproxy.lo
CC libcurl_la-cf-https-connect.lo
CC libcurl_la-cf-socket.lo
CC libcurl_la-cfilters.lo
CC libcurl_la-conncache.lo
CC libcurl_la-connect.lo
CC libcurl_la-content_encoding.lo
CC libcurl_la-cookie.lo
CC libcurl_la-curl_addrinfo.lo
CC libcurl_la-curl_des.lo
CC libcurl_la-curl_endian.lo
CC libcurl_la-curl_fnmatch.lo
CC libcurl_la-curl_get_line.lo
CC libcurl_la-curl_gethostname.lo
CC libcurl_la-curl_gssapi.lo
CC libcurl_la-curl_memrchr.lo
CC libcurl_la-curl_multibyte.lo
CC libcurl_la-curl_ntlm_core.lo
CC libcurl_la-curl_range.lo
CC libcurl_la-curl_rtmp.lo
CC libcurl_la-curl_sasl.lo
CC libcurl_la-curl_sha512_256.lo
CC libcurl_la-curl_sspi.lo
CC libcurl_la-curl_threads.lo
CC libcurl_la-curl_trc.lo
CC libcurl_la-cw-out.lo
CC libcurl_la-dict.lo
CC libcurl_la-dllmain.lo
CC libcurl_la-doh.lo
CC libcurl_la-dynbuf.lo
CC libcurl_la-dynhds.lo
CC libcurl_la-easy.lo
CC libcurl_la-easygetopt.lo
CC libcurl_la-easyoptions.lo
CC libcurl_la-escape.lo
CC libcurl_la-file.lo
CC libcurl_la-fileinfo.lo
CC libcurl_la-fopen.lo
CC libcurl_la-formdata.lo
CC libcurl_la-ftp.lo
CC libcurl_la-ftplistparser.lo
CC libcurl_la-getenv.lo
CC libcurl_la-getinfo.lo
CC libcurl_la-gopher.lo
CC libcurl_la-hash.lo
CC libcurl_la-headers.lo
CC libcurl_la-hmac.lo
CC libcurl_la-hostasyn.lo
CC libcurl_la-hostip.lo
CC libcurl_la-hostip4.lo
CC libcurl_la-hostip6.lo
CC libcurl_la-hostsyn.lo
CC libcurl_la-hsts.lo
CC libcurl_la-http.lo
CC libcurl_la-http1.lo
CC libcurl_la-http2.lo
CC libcurl_la-http_aws_sigv4.lo
CC libcurl_la-http_chunks.lo
CC libcurl_la-http_digest.lo
CC libcurl_la-http_negotiate.lo
CC libcurl_la-http_ntlm.lo
CC libcurl_la-http_proxy.lo
CC libcurl_la-idn.lo
CC libcurl_la-if2ip.lo
CC libcurl_la-imap.lo
CC libcurl_la-inet_ntop.lo
CC libcurl_la-inet_pton.lo
CC libcurl_la-krb5.lo
CC libcurl_la-ldap.lo
CC libcurl_la-llist.lo
CC libcurl_la-macos.lo
CC libcurl_la-md4.lo
CC libcurl_la-md5.lo
CC libcurl_la-memdebug.lo
CC libcurl_la-mime.lo
CC libcurl_la-mprintf.lo
CC libcurl_la-mqtt.lo
CC libcurl_la-multi.lo
CC libcurl_la-netrc.lo
CC libcurl_la-nonblock.lo
CC libcurl_la-noproxy.lo
CC libcurl_la-openldap.lo
CC libcurl_la-parsedate.lo
CC libcurl_la-pingpong.lo
CC libcurl_la-pop3.lo
CC libcurl_la-progress.lo
CC libcurl_la-psl.lo
CC libcurl_la-rand.lo
CC libcurl_la-rename.lo
CC libcurl_la-request.lo
CC libcurl_la-rtsp.lo
CC libcurl_la-select.lo
CC libcurl_la-sendf.lo
CC libcurl_la-setopt.lo
CC libcurl_la-sha256.lo
CC libcurl_la-share.lo
CC libcurl_la-slist.lo
CC libcurl_la-smb.lo
CC libcurl_la-smtp.lo
CC libcurl_la-socketpair.lo
CC libcurl_la-socks.lo
CC libcurl_la-socks_gssapi.lo
CC libcurl_la-socks_sspi.lo
CC libcurl_la-speedcheck.lo
CC libcurl_la-splay.lo
CC libcurl_la-strcase.lo
CC libcurl_la-strdup.lo
CC libcurl_la-strerror.lo
CC libcurl_la-strparse.lo
CC libcurl_la-strtok.lo
CC libcurl_la-strtoofft.lo
CC libcurl_la-system_win32.lo
CC libcurl_la-telnet.lo
CC libcurl_la-tftp.lo
CC libcurl_la-timediff.lo
CC libcurl_la-timeval.lo
CC libcurl_la-transfer.lo
CC libcurl_la-url.lo
CC libcurl_la-urlapi.lo
CC libcurl_la-version.lo
CC libcurl_la-version_win32.lo
CC libcurl_la-warnless.lo
CC libcurl_la-ws.lo
CC vauth/libcurl_la-cleartext.lo
CC vauth/libcurl_la-cram.lo
CC vauth/libcurl_la-digest.lo
CC vauth/libcurl_la-digest_sspi.lo
CC vauth/libcurl_la-gsasl.lo
CC vauth/libcurl_la-krb5_gssapi.lo
CC vauth/libcurl_la-krb5_sspi.lo
CC vauth/libcurl_la-ntlm.lo
CC vauth/libcurl_la-ntlm_sspi.lo
CC vauth/libcurl_la-oauth2.lo
CC vauth/libcurl_la-spnego_gssapi.lo
CC vauth/libcurl_la-spnego_sspi.lo
CC vauth/libcurl_la-vauth.lo
CC vtls/libcurl_la-bearssl.lo
CC vtls/libcurl_la-cipher_suite.lo
CC vtls/libcurl_la-gtls.lo
CC vtls/libcurl_la-hostcheck.lo
CC vtls/libcurl_la-keylog.lo
CC vtls/libcurl_la-mbedtls.lo
CC vtls/libcurl_la-mbedtls_threadlock.lo
CC vtls/libcurl_la-openssl.lo
CC vtls/libcurl_la-rustls.lo
CC vtls/libcurl_la-schannel.lo
CC vtls/libcurl_la-schannel_verify.lo
CC vtls/libcurl_la-sectransp.lo
CC vtls/libcurl_la-vtls.lo
CC vtls/libcurl_la-wolfssl.lo
CC vtls/libcurl_la-vtls_scache.lo
CC vtls/libcurl_la-x509asn1.lo
CC vquic/libcurl_la-curl_msh3.lo
CC vquic/libcurl_la-curl_ngtcp2.lo
CC vquic/libcurl_la-curl_osslq.lo
CC vquic/libcurl_la-curl_quiche.lo
CC vquic/libcurl_la-vquic.lo
CC vquic/libcurl_la-vquic-tls.lo
CC vssh/libcurl_la-libssh.lo
CC vssh/libcurl_la-libssh2.lo
CC vssh/libcurl_la-curl_path.lo
CC vssh/libcurl_la-wolfssh.lo
CCLD libcurl.la
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/lib'
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/lib'
Making all in docs
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
Making all in .
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
make[2]: Nothing to be done for 'all-am'.
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
Making all in cmdline-opts
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
Making all in libcurl
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl'
Making all in opts
make[3]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl/opts'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl/opts'
make[3]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl'
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/libcurl'
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
Making all in src
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/src'
CC slist_wc.o
CC terminal.o
CC tool_cb_dbg.o
CC tool_bname.o
CC tool_cb_hdr.o
CC tool_cb_prg.o
CC tool_cb_rea.o
CC tool_cb_soc.o
CC tool_cb_see.o
CC tool_cb_wrt.o
CC tool_cfgable.o
CC tool_dirhie.o
CC tool_doswin.o
CC tool_easysrc.o
CC tool_filetime.o
CC tool_findfile.o
CC tool_formparse.o
CC tool_getparam.o
CC tool_getpass.o
CC tool_help.o
CC tool_helpers.o
echo '#include "tool_hugehelp.h"' >> tool_hugehelp.c
CC tool_ipfs.o
CC tool_libinfo.o
CC tool_listhelp.o
CC tool_main.o
CC tool_msgs.o
CC tool_operate.o
CC tool_operhlp.o
CC tool_paramhlp.o
CC tool_parsecfg.o
CC tool_progress.o
CC tool_setopt.o
CC tool_sleep.o
CC tool_stderr.o
CC tool_strdup.o
CC tool_urlglob.o
CC tool_util.o
CC tool_vms.o
CC tool_writeout.o
CC tool_writeout_json.o
CC var.o
CC tool_xattr.o
echo 'extern const void *curl_ca_embed; const void *curl_ca_embed;' > tool_ca_embed.c
CC tool_hugehelp.o
CC ../lib/base64.o
CC tool_ca_embed.o
CC ../lib/dynbuf.o
CC ../lib/curl_multibyte.o
CC ../lib/nonblock.o
CC ../lib/strtoofft.o
CC ../lib/version_win32.o
CC ../lib/timediff.o
CC ../lib/warnless.o
CCLD curl
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/src'
Making all in scripts
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/scripts'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/scripts'
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0'
make[1]: Nothing to be done for 'all-am'.
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0'

Commit Diff GitHub →

.github/scripts/badwords.pl+13 -1

@@ -8,13 +8,21 @@
	# If separator is '=', the string will be compared case sensitively.
	# If separator is ':', the check is done case insensitively.
	#
+	# To add white listed uses of bad words that are removed before checking for
+	# the bad ones:
+	#
+	# ---(accepted word)
+	#
	my $w;
	while(<STDIN>) {
	chomp;
	if($_ =~ /^#/) {
	next;
	}
-	if($_ =~ /^([^:=])([:=])(.)/) {
+	if($_ =~ /^---(.*)/) {
+	push @whitelist, $1;
+	}
+	elsif($_ =~ /^([^:=])([:=])(.)/) {
	my ($bad, $sep, $better)=($1, $2, $3);
	push @w, $bad;
	$alt{$bad} = $better;
@@ -41,6 +49,10 @@ sub file {
	$in =~ s/(\[.\])$.$/$1/g;
	# remove backticked texts
	$in =~ s/\`.*\`//g;
+	# remove whitelisted patterns
+	for my $p (@whitelist) {
+	$in =~ s/$p//g;
+	}
	foreach my $w (@w) {
	my $case = $exactcase{$w};
	if(($in =~ /^(.*)$w/i && !$case) \|\|

.github/scripts/badwords.txt+5 -0

@@ -66,3 +66,8 @@ couldn't:could not
	64-bits:64 bits or 64-bit
	32-bits:32 bits or 32-bit
	\bvery\b:rephrase using an alternative word
+	\bCurl\b=curl
+	\bLibcurl\b=libcurl
+	---WWW::Curl
+	---NET::Curl
+	---Curl Corporation

.github/workflows/checkdocs.yml+1 -1

@@ -137,7 +137,7 @@ jobs:
	name: checkout

	- name: badwords
-	run: .github/scripts/badwords.pl < .github/scripts/badwords.txt docs/.md docs/libcurl/.md docs/libcurl/opts/.md docs/cmdline-opts/.md docs/TODO docs/KNOWN_BUGS tests/*.md
+	run: .github/scripts/badwords.pl < .github/scripts/badwords.txt `git ls-files '**.md'` docs/TODO docs/KNOWN_BUGS packages/OS400/README.OS400

	- name: verify-synopsis
	run: .github/scripts/verify-synopsis.pl docs/libcurl/curl*.md

GIT-INFO.md+1 -1

@@ -21,7 +21,7 @@ Daniel uses a configure line similar to this for easier development:

	./configure --disable-shared --enable-debug --enable-maintainer-mode

-	In environments that don't support configure (i.e. Windows), do this:
+	In environments that do not support configure (i.e. Windows), do this:

	buildconf.bat

README.md+2 -2

@@ -6,7 +6,7 @@ SPDX-License-Identifier: curl

	# [![curl logo](https://curl.se/logo/curl-logo.svg)](https://curl.se/)

-	Curl is a command-line tool for transferring data specified with URL syntax.
+	curl is a command-line tool for transferring data specified with URL syntax.
	Learn how to use curl by reading [the
	manpage](https://curl.se/docs/manpage.html) or [everything
	curl](https://everything.curl.dev/).
@@ -55,7 +55,7 @@ page](https://hackerone.com/curl) and not in public.

	## Notice

-	Curl contains pieces of source code that is Copyright (c) 1998, 1999 Kungliga
+	curl contains pieces of source code that is Copyright (c) 1998, 1999 Kungliga
	Tekniska Högskolan. This notice is included here to comply with the
	distribution terms.

docs/BUGS.md+1 -1

@@ -8,7 +8,7 @@ SPDX-License-Identifier: curl

	## There are still bugs

-	Curl and libcurl keep being developed. Adding features and changing code
+	curl and libcurl keep being developed. Adding features and changing code
	means that bugs sneak in, no matter how hard we try to keep them out.

	Of course there are lots of bugs left. Not to mention misfeatures.

docs/ECH.md+2 -2

@@ -59,7 +59,7 @@ not be the best solution.

	## Using ECH and DoH

-	Curl supports using DoH for A/AAAA lookups so it was relatively easy to add
+	curl supports using DoH for A/AAAA lookups so it was relatively easy to add
	retrieval of HTTPS RRs in that situation. To use ECH and DoH together:

	```bash
@@ -153,7 +153,7 @@ For now, this only works for the OpenSSL and BoringSSL/AWS-LC builds.

	## Default settings

-	Curl has various ways to configure default settings, e.g. in ``$HOME/.curlrc``,
+	curl has various ways to configure default settings, e.g. in ``$HOME/.curlrc``,
	so one can set the DoH URL and enable ECH that way:

	```bash

docs/HISTORY.md+3 -3

@@ -74,7 +74,7 @@ November: configure script and reported successful compiles on several
	major operating systems. The never-quite-understood -F option was added and
	curl could now simulate quite a lot of a browser. TELNET support was added.

-	Curl 5 was released in December 1998 and introduced the first ever curl man
+	curl 5 was released in December 1998 and introduced the first ever curl man
	page. People started making Linux RPM packages out of it.

	1999
@@ -187,7 +187,7 @@ June: curl 7.12.0 introduced IDN support. 10 official web mirrors.
	This release bumped the major SONAME to 3 due to the removal of the
	`curl_formparse()` function

-	August: Curl and libcurl 7.12.1
+	August: curl and libcurl 7.12.1

	Public curl release number: 82
	Releases counted from the beginning: 109
@@ -377,7 +377,7 @@ April: added the cyassl backend (later renamed to wolfSSL)
	curl and libcurl are installed in an estimated 5 billion instances
	world-wide.

-	October 31: Curl and libcurl 7.62.0
+	October 31: curl and libcurl 7.62.0

	Public curl releases: 177
	Command line options: 219

docs/MANUAL.md+16 -16

@@ -115,7 +115,7 @@ matching public key file must be specified using the `--pubkey` option.

	### HTTP

-	Curl also supports user and password in HTTP URLs, thus you can pick a file
+	curl also supports user and password in HTTP URLs, thus you can pick a file
	like:

	curl http://name:[email protected]/full/path/to/file
@@ -170,7 +170,7 @@ curl uses HTTP/1.0 instead of HTTP/1.1 for any `CONNECT` attempts.

	curl also supports SOCKS4 and SOCKS5 proxies with `--socks4` and `--socks5`.

-	See also the environment variables Curl supports that offer further proxy
+	See also the environment variables curl supports that offer further proxy
	control.

	Most FTP proxy servers are set up to appear as a normal FTP server from the
@@ -199,7 +199,7 @@ should be read from STDIN.
	## Ranges

	HTTP 1.1 introduced byte-ranges. Using this, a client can request to get only
-	one or more sub-parts of a specified document. Curl supports this with the
+	one or more sub-parts of a specified document. curl supports this with the
	`-r` flag.

	Get the first 100 bytes of a document:
@@ -210,7 +210,7 @@ Get the last 500 bytes of a document:

	curl -r -500 http://www.example.com/

-	Curl also supports simple ranges for FTP files as well. Then you can only
+	curl also supports simple ranges for FTP files as well. Then you can only
	specify start and stop position.

	Get the first 100 bytes of a document using FTP:
@@ -238,7 +238,7 @@ Upload a local file to get appended to the remote file:

	curl -T localfile -a ftp://ftp.example.com/remotefile

-	Curl also supports ftp upload through a proxy, but only if the proxy is
+	curl also supports ftp upload through a proxy, but only if the proxy is
	configured to allow that kind of tunneling. If it does, you can run curl in a
	fashion similar to:

@@ -264,7 +264,7 @@ For other ways to do HTTP data upload, see the POST section below.

	If curl fails where it is not supposed to, if the servers do not let you in,
	if you cannot understand the responses: use the `-v` flag to get verbose
-	fetching. Curl outputs lots of info and what it sends and receives in order to
+	fetching. curl outputs lots of info and what it sends and receives in order to
	let the user see all client-server interaction (but it does not show you the
	actual data).

@@ -286,7 +286,7 @@ info on a single file for HTTP and FTP. The HTTP information is a lot more
	extensive.

	For HTTP, you can get the header information (the same as `-I` would show)
-	shown before the data by using `-i`/`--include`. Curl understands the
+	shown before the data by using `-i`/`--include`. curl understands the
	`-D`/`--dump-header` option when getting files from both FTP and HTTP, and it
	then stores the headers in the specified file.

@@ -407,7 +407,7 @@ contain certain data.
	## User Agent

	An HTTP request has the option to include information about the browser that
-	generated the request. Curl allows it to be specified on the command line. It
+	generated the request. curl allows it to be specified on the command line. It
	is especially useful to fool or trick stupid servers or CGI scripts that only
	accept certain browsers.

@@ -456,7 +456,7 @@ Example, get a page that wants my name passed in a cookie:

	curl -b "name=Daniel" www.example.com

-	Curl also has the ability to use previously received cookies in following
+	curl also has the ability to use previously received cookies in following
	sessions. If you get cookies from a server and store them in a file in a
	manner similar to:

@@ -482,7 +482,7 @@ non-existing file to trigger the cookie awareness like:
	curl -L -b empty.txt www.example.com

	The file to read cookies from must be formatted using plain HTTP headers OR as
-	Netscape's cookie file. Curl determines what kind it is based on the file
+	Netscape's cookie file. curl determines what kind it is based on the file
	contents. In the above command, curl parses the header and store the cookies
	received from www.example.com. curl sends the stored cookies which match the
	request to the server as it follows the location. The file `empty.txt` may be
@@ -523,7 +523,7 @@ much explanation!

	## Speed Limit

-	Curl allows the user to set the transfer speed conditions that must be met to
+	curl allows the user to set the transfer speed conditions that must be met to
	let the transfer keep going. By using the switch `-y` and `-Y` you can make
	curl abort transfers if the transfer speed is below the specified lowest limit
	for a specified time.
@@ -562,7 +562,7 @@ stalls during periods.

	## Config File

-	Curl automatically tries to read the `.curlrc` file (or `_curlrc` file on
+	curl automatically tries to read the `.curlrc` file (or `_curlrc` file on
	Microsoft Windows systems) from the user's home directory on startup.

	The config file could be made up with normal command line switches, but you
@@ -822,7 +822,7 @@ with current logon credentials (SSPI/SPNEGO).

	## Environment Variables

-	Curl reads and understands the following environment variables:
+	curl reads and understands the following proxy related environment variables:

	http_proxy, HTTPS_PROXY, FTP_PROXY

@@ -855,7 +855,7 @@ this is a big security risk if someone else gets hold of your passwords,
	therefore most Unix programs do not read this file unless it is only readable
	by yourself (curl does not care though).

-	Curl supports `.netrc` files if told to (using the `-n`/`--netrc` and
+	curl supports `.netrc` files if told to (using the `-n`/`--netrc` and
	`--netrc-optional` options). This is not restricted to just FTP, so curl can
	use it for all protocols where authentication is used.

@@ -876,7 +876,7 @@ ending newline:

	## Kerberos FTP Transfer

-	Curl supports kerberos4 and kerberos5/GSSAPI for FTP transfers. You need the
+	curl supports kerberos4 and kerberos5/GSSAPI for FTP transfers. You need the
	kerberos package installed and used at curl build time for it to be available.

	First, get the krb-ticket the normal way, like with the `kinit`/`kauth` tool.
@@ -889,7 +889,7 @@ ask for one and you already entered the real password to `kinit`/`kauth`.

	## TELNET

-	The curl telnet support is basic and easy to use. Curl passes all data passed
+	The curl telnet support is basic and easy to use. curl passes all data passed
	to it on stdin to the remote server. Connect to a remote telnet server using a
	command line similar to:

docs/RUSTLS.md+1 -1

@@ -6,7 +6,7 @@ SPDX-License-Identifier: curl

	# Rustls

-	[Rustls is a TLS backend written in Rust](https://docs.rs/rustls/). Curl can
+	[Rustls is a TLS backend written in Rust](https://docs.rs/rustls/). curl can
	be built to use it as an alternative to OpenSSL or other TLS backends. We use
	the [rustls-ffi C bindings](https://github.com/rustls/rustls-ffi/). This
	version of curl depends on version v0.14.0 of rustls-ffi.

docs/TheArtOfHttpScripting.md+10 -10

@@ -4,7 +4,7 @@ Copyright (C) Daniel Stenberg, <[email protected]>, et al.
	SPDX-License-Identifier: curl
	-->

-	# The Art Of Scripting HTTP Requests Using Curl
+	# The Art Of Scripting HTTP Requests Using curl

	## Background

@@ -15,12 +15,12 @@ SPDX-License-Identifier: curl
	extract information from the web, to fake users, to post or upload data to
	web servers are all important tasks today.

-	Curl is a command line tool for doing all sorts of URL manipulations and
+	curl is a command line tool for doing all sorts of URL manipulations and
	transfers, but this particular document focuses on how to use it when doing
	HTTP requests for fun and profit. This documents assumes that you know how to
	invoke `curl --help` or `curl --manual` to get basic information about it.

-	Curl is not written to do everything for you. It makes the requests, it gets
+	curl is not written to do everything for you. It makes the requests, it gets
	the data, it sends data and it retrieves the information. You probably need
	to glue everything together using some kind of script language or repeated
	manual invokes.
@@ -475,7 +475,7 @@ SPDX-License-Identifier: curl
	new page keeping newly generated output. The header that tells the browser to
	redirect is `Location:`.

-	Curl does not follow `Location:` headers by default, but simply displays such
+	curl does not follow `Location:` headers by default, but simply displays such
	pages in the same manner it displays all HTTP replies. It does however
	feature an option that makes it attempt to follow the `Location:` pointers.

@@ -485,7 +485,7 @@ SPDX-License-Identifier: curl

	If you use curl to POST to a site that immediately redirects you to another
	page, you can safely use [`--location`](https://curl.se/docs/manpage.html#-L)
-	(`-L`) and `--data`/`--form` together. Curl only uses POST in the first
+	(`-L`) and `--data`/`--form` together. curl only uses POST in the first
	request, and then revert to GET in the following operations.

	## Other redirects
@@ -532,7 +532,7 @@ SPDX-License-Identifier: curl
	[`--cookie-jar`](https://curl.se/docs/manpage.html#-c) option described
	below is a better way to store cookies.)

-	Curl has a full blown cookie parsing engine built-in that comes in use if you
+	curl has a full blown cookie parsing engine built-in that comes in use if you
	want to reconnect to a server and use cookies that were stored from a
	previous connection (or hand-crafted manually to fool the server into
	believing you had a previous connection). To use previously stored cookies,
@@ -540,7 +540,7 @@ SPDX-License-Identifier: curl

	curl --cookie stored_cookies_in_file http://www.example.com

-	Curl's "cookie engine" gets enabled when you use the
+	curl's "cookie engine" gets enabled when you use the
	[`--cookie`](https://curl.se/docs/manpage.html#-b) option. If you only
	want curl to understand received cookies, use `--cookie` with a file that
	does not exist. Example, if you want to let curl understand cookies from a
@@ -549,7 +549,7 @@ SPDX-License-Identifier: curl

	curl --cookie nada --location http://www.example.com

-	Curl has the ability to read and write cookie files that use the same file
+	curl has the ability to read and write cookie files that use the same file
	format that Netscape and Mozilla once used. It is a convenient way to share
	cookies between scripts or invokes. The `--cookie` (`-b`) switch
	automatically detects if a given file is such a cookie file and parses it,
@@ -571,7 +571,7 @@ SPDX-License-Identifier: curl
	SSL (or TLS as the current version of the standard is called) offers a set of
	advanced features to do secure transfers over HTTP.

-	Curl supports encrypted fetches when built to use a TLS library and it can be
+	curl supports encrypted fetches when built to use a TLS library and it can be
	built to use one out of a fairly large set of libraries - `curl -V` shows
	which one your curl was built to use (if any). To get a page from an HTTPS
	server, simply run curl like:
@@ -581,7 +581,7 @@ SPDX-License-Identifier: curl
	## Certificates

	In the HTTPS world, you use certificates to validate that you are the one you
-	claim to be, as an addition to normal passwords. Curl supports client- side
+	claim to be, as an addition to normal passwords. curl supports client- side
	certificates. All certificates are locked with a passphrase, which you need
	to enter before the certificate can be used by curl. The passphrase can be
	specified on the command line or if not, entered interactively when curl

docs/VERSIONS.md+1 -1

@@ -7,7 +7,7 @@ SPDX-License-Identifier: curl
	Version Numbers and Releases
	============================

-	Curl is not only curl. Curl is also libcurl. They are actually individually
+	The command line tool curl and the library libcurl are individually
	versioned, but they usually follow each other closely.

	The version numbering is always built up using the same system:

docs/cmdline-opts/_EXITCODES.md+4 -4

@@ -33,14 +33,14 @@ FTP accept failed. While waiting for the server to connect back when an active
	FTP session is used, an error code was sent over the control connection or
	similar.
	## 11
-	FTP weird PASS reply. Curl could not parse the reply sent to the PASS request.
+	FTP weird PASS reply. curl could not parse the reply sent to the PASS request.
	## 12
	During an active FTP session while waiting for the server to connect back to
	curl, the timeout expired.
	## 13
-	FTP weird PASV reply, Curl could not parse the reply sent to the PASV request.
+	FTP weird PASV reply, curl could not parse the reply sent to the PASV request.
	## 14
-	FTP weird 227 format. Curl could not parse the 227-line the server sent.
+	FTP weird 227 format. curl could not parse the 227-line the server sent.
	## 15
	FTP cannot use host. Could not resolve the host IP we got in the 227-line.
	## 16
@@ -61,7 +61,7 @@ HTTP page not retrieved. The requested URL was not found or returned another
	error with the HTTP error code being 400 or above. This return code only
	appears if --fail is used.
	## 23
-	Write error. Curl could not write data to a local filesystem or similar.
+	Write error. curl could not write data to a local filesystem or similar.
	## 25
	Failed starting the upload. For FTP, the server typically denied the STOR
	command.

docs/cmdline-opts/cookie-jar.md+1 -1

@@ -20,7 +20,7 @@ Example:
	# `--cookie-jar`

	Specify to which file you want curl to write all cookies after a completed
-	operation. Curl writes all cookies from its in-memory cookie storage to the
+	operation. curl writes all cookies from its in-memory cookie storage to the
	given file at the end of operations. Even if no cookies are known, a file is
	created so that it removes any formerly existing cookies from the file. The
	file uses the Netscape cookie file format. If you set the filename to a single

docs/cmdline-opts/disable-eprt.md+1 -1

@@ -17,7 +17,7 @@ Example:
	# `--disable-eprt`

	Disable the use of the EPRT and LPRT commands when doing active FTP transfers.
-	Curl normally first attempts to use EPRT before using PORT, but with this
+	curl normally first attempts to use EPRT before using PORT, but with this
	option, it uses PORT right away. EPRT is an extension to the original FTP
	protocol, and does not work on all servers, but enables more functionality in
	a better way than the traditional PORT command.

docs/cmdline-opts/disable-epsv.md+1 -1

@@ -16,7 +16,7 @@ Example:

	# `--disable-epsv`

-	Disable the use of the EPSV command when doing passive FTP transfers. Curl
+	Disable the use of the EPSV command when doing passive FTP transfers. curl
	normally first attempts to use EPSV before PASV, but with this option, it does
	not try EPSV.

docs/cmdline-opts/hostpubsha256.md+1 -1

@@ -17,7 +17,7 @@ Example:
	# `--hostpubsha256`

	Pass a string containing a Base64-encoded SHA256 hash of the remote host's
-	public key. Curl refuses the connection with the host unless the hashes match.
+	public key. curl refuses the connection with the host unless the hashes match.

	This feature requires libcurl to be built with libssh2 and does not work with
	other SSH backends.

docs/cmdline-opts/netrc.md+1 -1

@@ -21,7 +21,7 @@ Example:
	Make curl scan the .netrc file in the user's home directory for login name
	and password. This is typically used for FTP on Unix. If used with HTTP, curl
	enables user authentication. See netrc(5) and ftp(1) for details on the
-	file format. Curl does not complain if that file does not have the right
+	file format. curl does not complain if that file does not have the right
	permissions (it should be neither world- nor group-readable). The environment
	variable "HOME" is used to find the home directory.

docs/cmdline-opts/silent.md+1 -1

@@ -17,7 +17,7 @@ Example:

	# `--silent`

-	Silent or quiet mode. Do not show progress meter or error messages. Makes Curl
+	Silent or quiet mode. Do not show progress meter or error messages. Makes curl
	mute. It still outputs the data you ask for, potentially even to the
	terminal/stdout unless you redirect it.

docs/curl-config.md+1 -1

@@ -66,7 +66,7 @@ link your application with libcurl.

	## --prefix

-	This is the prefix used when libcurl was installed. Libcurl is then installed
+	This is the prefix used when libcurl was installed. libcurl is then installed
	in $prefix/lib and its header files are installed in $prefix/include and so
	on. The prefix is set with "configure --prefix".

docs/examples/multi-app.c+1 -1

@@ -52,7 +52,7 @@ int main(void)
	CURLMsg msg; / for picking up messages with the transfer status */
	int msgs_left; /* how many messages are left */

-	/* Allocate one CURL handle per transfer */
+	/* Allocate one curl handle per transfer */
	for(i = 0; i < HANDLECOUNT; i++)
	handles[i] = curl_easy_init();

docs/examples/multi-legacy.c+2 -2

@@ -58,7 +58,7 @@ int main(void)
	CURLMsg msg; / for picking up messages with the transfer status */
	int msgs_left; /* how many messages are left */

-	/* Allocate one CURL handle per transfer */
+	/* Allocate one curl handle per transfer */
	for(i = 0; i < HANDLECOUNT; i++)
	handles[i] = curl_easy_init();

@@ -183,7 +183,7 @@ int main(void)

	curl_multi_cleanup(multi_handle);

-	/* Free the CURL handles */
+	/* Free the curl handles */
	for(i = 0; i < HANDLECOUNT; i++)
	curl_easy_cleanup(handles[i]);

docs/internals/BUFQ.md+4 -5

@@ -11,8 +11,8 @@ to and read from. It manages read and write positions and has a maximum size.

	## read/write

-	Its basic read/write functions have a similar signature and return code handling
-	as many internal Curl read and write ones.
+	Its basic read/write functions have a similar signature and return code
+	handling as many internal curl read and write ones.


	```
@@ -84,9 +84,8 @@ It is possible to undo writes by calling:
	CURLcode Curl_bufq_unwrite(struct bufq *q, size_t len);
	```

-	This will remove `len` bytes from the end of the bufq again. When removing
-	more bytes than are present, CURLE_AGAIN is returned and the bufq will be
-	empty.
+	This removes `len` bytes from the end of the bufq again. When removing more
+	bytes than are present, CURLE_AGAIN is returned and bufq is cleared.

	## lifetime

docs/internals/LLIST.md+4 -5

@@ -65,12 +65,11 @@ See also `Curl_llist_insert_next`.
	## Remove a node

	Remove a node again from a list by calling `Curl_llist_remove()`. This
-	will destroy the node's `elem` (e.g. calling a registered free function).
+	destroys the node's `elem` (e.g. calling a registered free function).

-	To remove a node without destroying it's `elem`, use
-	`Curl_node_take_elem()` which returns the `elem` pointer and
-	removes the node from the list. The caller then owns this pointer
-	and has to take care of it.
+	To remove a node without destroying its `elem`, use `Curl_node_take_elem()`
+	which returns the `elem` pointer and removes the node from the list. The
+	caller then owns this pointer and has to take care of it.

	## Iterate

docs/internals/MQTT.md+4 -2

@@ -23,7 +23,8 @@ Example subscribe:

	curl mqtt://host.home/bedroom/temp

-	This will send an MQTT SUBSCRIBE packet for the topic `bedroom/temp` and listen in for incoming PUBLISH packets.
+	This sends an MQTT SUBSCRIBE packet for the topic `bedroom/temp` and listen in
+	for incoming PUBLISH packets.

	### Publishing

@@ -35,7 +36,8 @@ Example publish:

	curl -d 75 mqtt://host.home/bedroom/dimmer

-	This will send an MQTT PUBLISH packet to the topic `bedroom/dimmer` with the payload `75`.
+	This sends an MQTT PUBLISH packet to the topic `bedroom/dimmer` with the
+	payload `75`.

	## What does curl deliver as a response to a subscribe

docs/internals/TLS-SESSIONS.md+51 -56

@@ -27,7 +27,7 @@ for an insight into this topic.
	These difference between TLS protocol versions are reflected in curl's
	handling of session tickets. More below.

-	## Curl's `ssl_peer_key`
+	## curl's `ssl_peer_key`

	In order to find a ticket from a previous TLS session, curl
	needs a name for TLS sessions that uniquely identifies the peer
@@ -55,18 +55,18 @@ Examples:
	Different configurations produce different keys which is just what
	curl needs when handling SSL session tickets.

-	One important thing: peer keys do not contain confidential
-	information. If you configure a client certificate or SRP authentication
-	with username/password, these will not be part of the peer key.
+	One important thing: peer keys do not contain confidential information. If you
+	configure a client certificate or SRP authentication with username/password,
+	these are not part of the peer key.

	However, peer keys carry the hostnames you use curl for. The do
	leak the privacy of your communication. We recommend to not persist
	peer keys for this reason.

-	Caveat: The key may contain file names or paths. It does not
-	reflect the contents in the filesystem. If you change `/etc/ssl/cert.pem`
-	and reuse a previous ticket, curl might trust a server which no
-	longer has a root certificate in the file.
+	Caveat: The key may contain filenames or paths. It does not reflect the
+	contents in the filesystem. If you change `/etc/ssl/cert.pem` and reuse a
+	previous ticket, curl might trust a server which no longer has a root
+	certificate in the file.


	## Session Cache Access
@@ -76,22 +76,20 @@ longer has a root certificate in the file.
	When a new connection is being established, each SSL connection filter creates
	its own peer_key and calls into the cache. The cache then looks for a ticket
	with exactly this peer_key. Peer keys between proxy SSL filters and SSL
-	filters talking through a tunnel will differ, as they talk to different
-	peers.
+	filters talking through a tunnel differ, as they talk to different peers.

	If the connection filter wants to use a client certificate or SRP
-	authentication, the cache will check those as well. If the cache peer
-	carries client cert or SRP auth, the connection filter must have
-	those with the same values (and vice versa).
-
-	On a match, the connection filter gets the session ticket and feeds that
-	to the TLS implementation which, on accepting it, will try to resume it
-	for a shorter handshake. In addition, the filter gets the ALPN used
-	before and the amount of 0-RTT data that the server announced to be
-	willing to accept. The filter can then decide if it wants to attempt
-	0-RTT or not. (The ALPN is needed to know if the server speaks the
-	protocol you want to send in 0-RTT. It makes no sense to send HTTP/2
-	requests to a server that only knows HTTP/1.1.)
+	authentication, the cache checks those as well. If the cache peer carries
+	client cert or SRP auth, the connection filter must have those with the same
+	values (and vice versa).
+
+	On a match, the connection filter gets the session ticket and feeds that to
+	the TLS implementation which, on accepting it, tries to resume it for a
+	shorter handshake. In addition, the filter gets the ALPN used before and the
+	amount of 0-RTT data that the server announced to be willing to accept. The
+	filter can then decide if it wants to attempt 0-RTT or not. (The ALPN is
+	needed to know if the server speaks the protocol you want to send in 0-RTT. It
+	makes no sense to send HTTP/2 requests to a server that only knows HTTP/1.1.)

	#### Updates

@@ -106,10 +104,10 @@ when a filter accesses the session cache, it takes
	a ticket from the cache, meaning a returned ticket is removed. The filter
	then configures its TLS backend and returns the ticket to the cache.

-	The cache needs to treat tickets from TLSv1.2 and 1.3 differently.
-	1.2 tickets should be reused, but 1.3 tickets SHOULD NOT (RFC 8446).
-	The session cache will simply drop 1.3 tickets when they are returned
-	after use, but keep a 1.2 ticket.
+	The cache needs to treat tickets from TLSv1.2 and 1.3 differently. 1.2 tickets
+	should be reused, but 1.3 tickets SHOULD NOT (RFC 8446). The session cache
+	simply drops 1.3 tickets when they are returned after use, but keeps a 1.2
+	ticket.

	When a ticket is put into the cache, there is also a difference. There
	can be several 1.3 tickets at the same time, but only a single 1.2 ticket.
@@ -117,16 +115,16 @@ TLSv1.2 tickets replace any other. 1.3 tickets accumulate up to a max
	amount.

	By having a "put/take/return" we reflect the 1.3 use case nicely. Two
-	concurrent connections will not reuse the same ticket.
+	concurrent connections do not reuse the same ticket.

	## Session Ticket Persistence

	#### Privacy and Security

-	As mentioned above, ssl peer keys are not intended for storage in a
-	file system. They'll clearly show which hosts the user talked to. This
-	maybe "just" privacy relevant, but has security implications as an
-	attacker might find worthy targets among your peer keys.
+	As mentioned above, ssl peer keys are not intended for storage in a file
+	system. They clearly show which hosts the user talked to. This maybe "just"
+	privacy relevant, but has security implications as an attacker might find
+	worthy targets among your peer keys.

	Also, we do not recommend to persist TLSv1.2 tickets.

@@ -137,32 +135,29 @@ it provides a salted SHA256 hash of the peer key for import and export.

	#### Export

-	The salt is generated randomly for each peer key on export. The
-	SHA256 makes sure that the peer key cannot be reversed and that
-	a slightly different key still produces a very different result.
+	The salt is generated randomly for each peer key on export. The SHA256 makes
+	sure that the peer key cannot be reversed and that a slightly different key
+	still produces a different result.

-	This means an attacker cannot just "grep" a session file for a
-	particular entry, e.g. if they want to know if you accessed a
-	specific host. They can however compute the SHA256 hashes for
-	all salts in the file and find a specific entry. But they cannot
-	find a hostname they do not know. They'd have to brute force by
-	guessing.
+	This means an attacker cannot just "grep" a session file for a particular
+	entry, e.g. if they want to know if you accessed a specific host. They can
+	however compute the SHA256 hashes for all salts in the file and find a
+	specific entry. They cannot find a hostname they do not know. They would
+	have to brute force by guessing.

	#### Import

-	When session tickets are imported from a file, curl only gets the
-	salted hashes. The tickets imported will belong to an unknown
-	peer key.
-
-	When a connection filter tries to take a session ticket, it will
-	pass its peer key. This peer key will initially not match any
-	tickets in the cache. The cache then checks all entries with
-	unknown peer keys if the passed key matches their salted hash. If
-	it does, the peer key is recovered and remembered at the cache
-	entry.
-
-	This is a performance penalty in the order of "unknown" peer keys
-	which will diminish over time when keys are rediscovered. Note that
-	this also works for putting a new ticket into the cache: when no
-	present entry matches, a new one with peer key is created. This
-	peer key will then no longer bear the cost of hash computes.
+	When session tickets are imported from a file, curl only gets the salted
+	hashes. The imported tickets belong to an unknown peer key.
+
+	When a connection filter tries to take a session ticket, it passes its peer
+	key. This peer key initially does not match any tickets in the cache. The
+	cache then checks all entries with unknown peer keys if the passed key matches
+	their salted hash. If it does, the peer key is recovered and remembered at the
+	cache entry.
+
+	This is a performance penalty in the order of "unknown" peer keys which
+	diminishes over time when keys are rediscovered. Note that this also works for
+	putting a new ticket into the cache: when no present entry matches, a new one
+	with peer key is created. This peer key then no longer bears the cost of hash
+	computes.

docs/libcurl/curl_easy_init.md+2 -2

@@ -30,8 +30,8 @@ CURL *curl_easy_init();

	# DESCRIPTION

-	This function allocates and returns a CURL easy handle. Such a handle is used
-	as input to other functions in the easy interface. This call must have a
+	This function allocates and returns an easy handle. Such a handle is used as
+	input to other functions in the easy interface. This call must have a
	corresponding call to curl_easy_cleanup(3) when the operation is complete.

	The easy handle is used to hold and control a single network transfer. It is

docs/libcurl/curl_easy_reset.md+1 -1

@@ -28,7 +28,7 @@ void curl_easy_reset(CURL *handle);

	# DESCRIPTION

-	Re-initializes all options previously set on a specified CURL handle to the
+	Re-initializes all options previously set on a specified curl handle to the
	default values. This puts back the handle to the same state as it was in when
	it was just created with curl_easy_init(3).

docs/libcurl/opts/CURLINFO_CONTENT_TYPE.md+1 -1

@@ -35,7 +35,7 @@ protocol used does not support this.

	The ct pointer is set to NULL or pointing to private memory. You MUST
	NOT free it - it gets freed when you call curl_easy_cleanup(3) on the
-	corresponding CURL handle.
+	corresponding curl handle.

	The modern way to get this header from a response is to instead use the
	curl_easy_header(3) function.

docs/libcurl/opts/CURLINFO_EFFECTIVE_METHOD.md+1 -1

@@ -37,7 +37,7 @@ the same method the first request would use.

	The methodp pointer is NULL or points to private memory. You MUST NOT
	free - it gets freed when you call curl_easy_cleanup(3) on the
-	corresponding CURL handle.
+	corresponding curl handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_EFFECTIVE_URL.md+2 -2

@@ -33,8 +33,8 @@ In cases when you have asked libcurl to follow redirects, it may not be the same
	value you set with CURLOPT_URL(3).

	The urlp pointer is NULL or points to private memory. You MUST NOT free
-	- it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	- it gets freed when you call curl_easy_cleanup(3) on the corresponding curl
+	handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_FTP_ENTRY_PATH.md+2 -2

@@ -32,8 +32,8 @@ logging on to the remote FTP server. This stores a NULL as pointer if
	something is wrong.

	The path pointer is NULL or points to private memory. You MUST NOT free
-	- it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	- it gets freed when you call curl_easy_cleanup(3) on the corresponding curl
+	handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_PRIMARY_IP.md+3 -3

@@ -35,9 +35,9 @@ string holding the IP address of the most recent connection done with this
	get a pointer to a memory area that is reused at next request so you need to
	copy the string if you want to keep the information.

-	The ip pointer is NULL or points to private memory. You MUST NOT free -
-	it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	The ip pointer is NULL or points to private memory. You MUST NOT free - it
+	gets freed when you call curl_easy_cleanup(3) on the corresponding curl
+	handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_REFERER.md+2 -2

@@ -32,8 +32,8 @@ Pass in a pointer to a char pointer and get the referrer header used in the
	most recent request.

	The hdrp pointer is NULL or points to private memory you MUST NOT free -
-	it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	it gets freed when you call curl_easy_cleanup(3) on the corresponding curl
+	handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_RTSP_SESSION_ID.md+3 -3

@@ -33,9 +33,9 @@ most recent RTSP Session ID.
	Applications wishing to resume an RTSP session on another connection should
	retrieve this info before closing the active connection.

-	The id pointer is NULL or points to private memory. You MUST NOT free -
-	it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	The id pointer is NULL or points to private memory. You MUST NOT free - it
+	gets freed when you call curl_easy_cleanup(3) on the corresponding curl
+	handle.

	# %PROTOCOLS%

docs/libcurl/opts/CURLINFO_SCHEME.md+1 -1

@@ -35,7 +35,7 @@ this CURL handle.

	The scheme pointer is NULL or points to private memory. You MUST NOT
	free - it gets freed when you call curl_easy_cleanup(3) on the corresponding
-	CURL handle.
+	curl handle.

	The returned scheme might be upper or lowercase. Do comparisons case
	insensitively.

docs/libcurl/opts/CURLMOPT_PUSHFUNCTION.md+1 -1

@@ -77,7 +77,7 @@ introduced in later libcurl versions.
	## CURL_PUSH_OK (0)

	The application has accepted the stream and it can now start receiving data,
-	the ownership of the CURL handle has been taken over by the application.
+	the ownership of the curl handle has been taken over by the application.

	## CURL_PUSH_DENY (1)

docs/libcurl/opts/CURLOPT_DOH_SSL_VERIFYHOST.md+2 -2

@@ -42,9 +42,9 @@ When CURLOPT_DOH_SSL_VERIFYHOST(3) is 2, the SSL certificate provided by
	the DoH server must indicate that the server name is the same as the server
	name to which you meant to connect to, or the connection fails.

-	Curl considers the DoH server the intended one when the Common Name field or a
+	curl considers the DoH server the intended one when the Common Name field or a
	Subject Alternate Name field in the certificate matches the hostname in the
-	DoH URL to which you told Curl to connect.
+	DoH URL to which you told curl to connect.

	When the verify value is set to 1L it is treated the same as 2L. However
	for consistency with the other VERIFYHOST options we suggest use 2 and

docs/libcurl/opts/CURLOPT_DOH_SSL_VERIFYPEER.md+1 -1

@@ -44,7 +44,7 @@ This option is the DoH equivalent of CURLOPT_SSL_VERIFYPEER(3) and
	only affects requests to the DoH server.

	When negotiating a TLS or SSL connection, the server sends a certificate
-	indicating its identity. Curl verifies whether the certificate is authentic,
+	indicating its identity. curl verifies whether the certificate is authentic,
	i.e. that you can trust that the server is who the certificate says it is.
	This trust is based on a chain of digital signatures, rooted in certification
	authority (CA) certificates you supply. curl uses a default bundle of CA

docs/libcurl/opts/CURLOPT_HTTP_CONTENT_DECODING.md+1 -1

@@ -29,7 +29,7 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_HTTP_CONTENT_DECODING,
	# DESCRIPTION

	Pass a long to tell libcurl how to act on content decoding. If set to zero,
-	content decoding is disabled. If set to 1 it is enabled. Libcurl has no
+	content decoding is disabled. If set to 1 it is enabled. libcurl has no
	default content decoding but requires you to use
	CURLOPT_ACCEPT_ENCODING(3) for that.

docs/libcurl/opts/CURLOPT_INTERLEAVEFUNCTION.md+1 -1

@@ -35,7 +35,7 @@ shown above.

	This callback function gets called by libcurl as soon as it has received
	interleaved RTP data. This function gets called for each $ block and therefore
-	contains exactly one upper-layer protocol unit (e.g. one RTP packet). Curl
+	contains exactly one upper-layer protocol unit (e.g. one RTP packet). curl
	writes the interleaved header as well as the included data for each call. The
	first byte is always an ASCII dollar sign. The dollar sign is followed by a
	one byte channel identifier and then a 2 byte integer length in network byte

docs/libcurl/opts/CURLOPT_PROXY_SSL_VERIFYHOST.md+1 -1

@@ -41,7 +41,7 @@ When CURLOPT_PROXY_SSL_VERIFYHOST(3) is 2, the proxy certificate must
	indicate that the server is the proxy to which you meant to connect to, or the
	connection fails.

-	Curl considers the proxy the intended one when the Common Name field or a
+	curl considers the proxy the intended one when the Common Name field or a
	Subject Alternate Name field in the certificate matches the hostname in the
	proxy string which you told curl to use.

docs/libcurl/opts/CURLOPT_PROXY_SSL_VERIFYPEER.md+1 -1

@@ -39,7 +39,7 @@ This is the proxy version of CURLOPT_SSL_VERIFYPEER(3) that is used for
	ordinary HTTPS servers.

	When negotiating a TLS or SSL connection, the server sends a certificate
-	indicating its identity. Curl verifies whether the certificate is authentic,
+	indicating its identity. curl verifies whether the certificate is authentic,
	i.e. that you can trust that the server is who the certificate says it is.
	This trust is based on a chain of digital signatures, rooted in certification
	authority (CA) certificates you supply. curl uses a default bundle of CA

docs/libcurl/opts/CURLOPT_SSH_KEYFUNCTION.md+5 -5

@@ -65,11 +65,11 @@ It gets called when the known_host matching has been done, to allow the
	application to act and decide for libcurl how to proceed. The callback is only
	called if CURLOPT_SSH_KNOWNHOSTS(3) is also set.

-	This callback function gets passed the CURL handle, the key from the
-	known_hosts file knownkey, the key from the remote site foundkey,
-	info from libcurl on the matching status and a custom pointer (set with
-	CURLOPT_SSH_KEYDATA(3)). It MUST return one of the following return
-	codes to tell libcurl how to act:
+	This callback function gets passed the curl handle, the key from the
+	known_hosts file knownkey, the key from the remote site foundkey, info
+	from libcurl on the matching status and a custom pointer (set with
+	CURLOPT_SSH_KEYDATA(3)). It MUST return one of the following return codes to
+	tell libcurl how to act:

	## CURLKHSTAT_FINE_REPLACE

docs/libcurl/opts/CURLOPT_SSL_VERIFYPEER.md+1 -1

@@ -38,7 +38,7 @@ This option determines whether curl verifies the authenticity of the peer's
	certificate. A value of 1 means curl verifies; 0 (zero) means it does not.

	When negotiating a TLS or SSL connection, the server sends a certificate
-	indicating its identity. Curl verifies whether the certificate is authentic,
+	indicating its identity. curl verifies whether the certificate is authentic,
	i.e. that you can trust that the server is who the certificate says it is.
	This trust is based on a chain of digital signatures, rooted in certification
	authority (CA) certificates you supply. curl uses a default bundle of CA

docs/libcurl/opts/CURLOPT_STREAM_DEPENDS_E.md+1 -1

@@ -29,7 +29,7 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_STREAM_DEPENDS_E,

	# DESCRIPTION

-	Pass a CURL pointer in dephandle to identify the stream within the same
+	Pass a `CURL` pointer in dephandle to identify the stream within the same
	connection that this stream is depending upon exclusively. That means it
	depends on it and sets the Exclusive bit.

include/curl/curl.h+2 -2

@@ -1959,10 +1959,10 @@ typedef enum {
	/* Set stream weight, 1 - 256 (default is 16) */
	CURLOPT(CURLOPT_STREAM_WEIGHT, CURLOPTTYPE_LONG, 239),

-	/* Set stream dependency on another CURL handle */
+	/* Set stream dependency on another curl handle */
	CURLOPT(CURLOPT_STREAM_DEPENDS, CURLOPTTYPE_OBJECTPOINT, 240),

-	/* Set E-xclusive stream dependency on another CURL handle */
+	/* Set E-xclusive stream dependency on another curl handle */
	CURLOPT(CURLOPT_STREAM_DEPENDS_E, CURLOPTTYPE_OBJECTPOINT, 241),

	/* Do not send any tftp option requests to the server */

include/curl/easy.h+1 -1

@@ -78,7 +78,7 @@ CURL_EXTERN CURL curl_easy_duphandle(CURL curl);
	*
	* DESCRIPTION
	*
-	* Re-initializes a CURL handle to the default values. This puts back the
+	* Re-initializes a curl handle to the default values. This puts back the
	* handle to the same state as it was in when it was just created.
	*
	* It does keep: live connections, the Session ID cache, the DNS cache and the

lib/macos.c+1 -1

@@ -37,7 +37,7 @@ CURLcode Curl_macos_init(void)
	/*
	* The automagic conversion from IPv4 literals to IPv6 literals only
	* works if the SCDynamicStoreCopyProxies system function gets called
-	* first. As Curl currently does not support system-wide HTTP proxies, we
+	* first. As curl currently does not support system-wide HTTP proxies, we
	* therefore do not use any value this function might return.
	*
	* This function is only available on macOS and is not needed for

lib/multi.c+1 -1

@@ -59,7 +59,7 @@
	/*
	CURL_SOCKET_HASH_TABLE_SIZE should be a prime number. Increasing it from 97
	to 911 takes on a 32-bit machine 4 x 804 = 3211 more bytes. Still, every
-	CURL handle takes 45-50 K memory, therefore this 3K are not significant.
+	curl handle takes 6K memory, therefore this 3K are not significant.
	*/
	#ifndef CURL_SOCKET_HASH_TABLE_SIZE
	#define CURL_SOCKET_HASH_TABLE_SIZE 911

lib/setup-vms.h+1 -1

@@ -370,7 +370,7 @@ static struct passwd *vms_getpwuid(uid_t uid)

	#define USE_UPPERCASE_KRBAPI 1

-	/* AI_NUMERICHOST needed for IP V6 support in Curl */
+	/* AI_NUMERICHOST needed for IP V6 support in curl */
	#ifdef HAVE_NETDB_H
	#include <netdb.h>
	#ifndef AI_NUMERICHOST

lib/vtls/openssl.h+1 -1

@@ -38,7 +38,7 @@

	struct ssl_peer;

-	/* Struct to hold a Curl OpenSSL instance */
+	/* Struct to hold a curl OpenSSL instance */
	struct ossl_ctx {
	/* these ones requires specific SSL-types */
	SSL_CTX* ssl_ctx;

packages/OS400/README.OS400+15 -15

@@ -4,10 +4,10 @@ Implementation notes:
	This is a true OS/400 ILE implementation, not a PASE implementation (for
	PASE, use AIX implementation).

-	The biggest problem with OS/400 is EBCDIC. Libcurl implements an internal
+	The biggest problem with OS/400 is EBCDIC. libcurl implements an internal
	conversion mechanism, but it has been designed for computers that have a
	single native character set. OS/400 default native character set varies
-	depending on the country for which it has been localized. And more, a job
+	depending on the country for which it has been localized. Further, a job
	may dynamically alter its "native" character set.
	Several characters that do not have fixed code in EBCDIC variants are
	used in libcurl strings. As a consequence, using the existing conversion
@@ -33,7 +33,7 @@ NOT converted, so text gathered this way is (probably !) ASCII.
	Another OS/400 problem comes from the fact that the last fixed argument of a
	vararg procedure may not be of type char, unsigned char, short or unsigned
	short. Enums that are internally implemented by the C compiler as one of these
-	types are also forbidden. Libcurl uses enums as vararg procedure tagfields...
+	types are also forbidden. libcurl uses enums as vararg procedure tagfields...
	Happily, there is a pragma forcing enums to type "int". The original libcurl
	header files are thus altered during build process to use this pragma, in
	order to force libcurl enums of being type int (the pragma disposition in use
@@ -201,7 +201,7 @@ _ curl_pushheader_bynum_cssid() and curl_pushheader_byname_ccsid()
	should be released with curl_free() after use, as opposite to the non-ccsid
	versions of these procedures.
	Please note that HTTP2 is not (yet) implemented on OS/400, thus these
-	functions will always return NULL.
+	functions always return NULL.

	_ curl_easy_option_by_name_ccsid() returns a pointer to an untranslated option
	metadata structure. As each curl_easyoption structure holds the option name in
@@ -216,15 +216,15 @@ hout parameter is kept in libcurl's encoding and should not be altered.
	_ curl_from_ccsid() and curl_to_ccsid() are string encoding conversion
	functions between ASCII (latin1) and the given CCSID. The first parameter is
	the source string, the second is the CCSID and the returned value is a pointer
-	to the dynamically allocated string. These functions do not impact on Curl's
+	to the dynamically allocated string. These functions do not impact on curl's
	behavior and are only provided for user convenience. After use, returned values
	must be released with curl_free().


-	Standard compilation environment does support neither autotools nor make;
-	in fact, very few common utilities are available. As a consequence, the
-	config-os400.h has been coded manually and the compilation scripts are
-	a set of shell scripts stored in subdirectory packages/OS400.
+	Standard compilation environment does support neither autotools nor make; in
+	fact, few common utilities are available. As a consequence, the config-os400.h
+	has been coded manually and the compilation scripts are a set of shell scripts
+	stored in subdirectory packages/OS400.

	The test environment is currently not supported on OS/400.

@@ -259,7 +259,7 @@ _ TFTP
	Compiling on OS/400:

	These instructions targets people who knows about OS/400, compiling, IFS and
-	archive extraction. Do not ask questions about these subjects if you're not
+	archive extraction. Do not ask questions about these subjects if you are not
	familiar with.

	_ As a prerequisite, QADRT development environment must be installed.
@@ -286,20 +286,20 @@ _ Enter the command "sh makefile.sh > makelog 2>&1"
	_ Examine the makelog file to check for compilation errors. CZM0383 warnings on
	C or system standard API come from QADRT inlining and can safely be ignored.

-	Without configuration parameters override, this will produce the following
+	Without configuration parameters override, this produces the following
	OS/400 objects:
-	_ Library CURL. All other objects will be stored in this library.
+	_ libcurl. All other objects are stored in this library.
	_ Modules for all libcurl units.
	_ Binding directory CURL_A, to be used at calling program link time for
	statically binding the modules (specify BNDSRVPGM(QADRTTS QGLDCLNT QGLDBRDR)
	when creating a program using CURL_A).
	_ Service program CURL.<soname>, where <soname> is extracted from the
-	lib/Makefile.am VERSION variable. To be used at calling program run-time
+	lib/Makefile.am VERSION variable. To be used at calling program runtime
	when this program has dynamically bound curl at link time.
	_ Binding directory CURL. To be used to dynamically bind libcurl when linking a
	calling program.
-	- CLI tool bound program CURL.
-	- CLI command CURL.
+	- CLI tool bound program curl.
+	- CLI command curl.
	_ Source file H. It contains all the include members needed to compile a C/C++
	module using libcurl, and an ILE/RPG /copy member for support in this
	language.

projects/README.md+19 -19

@@ -10,8 +10,8 @@ Building via IDE Project Files
	This document describes how to compile, build and install curl and libcurl
	from sources using legacy versions of Visual Studio 2010 - 2013.

-	You will need to generate the project files before using them. Please run
-	"generate -help" for usage details.
+	You need to generate the project files before using them. Please run "generate
+	-help" for usage details.

	To generate project files for recent versions of Visual Studio instead, use
	cmake. Refer to INSTALL-CMAKE in the docs directory.
@@ -43,7 +43,7 @@ a library is being compiled against dynamic runtime libraries.

	The projects files also support build configurations that require third party
	dependencies such as OpenSSL and libssh2. If you wish to support these, you
-	will also need to download and compile those libraries as well.
+	also need to download and compile those libraries as well.

	To support compilation of these libraries using different versions of
	compilers, the following directory structure has been used for both the output
@@ -70,19 +70,19 @@ of curl and libcurl as well as these dependencies.
	\|_VC <version>
	\|_<configuration>

-	As OpenSSL doesn't support side-by-side compilation when using different
-	versions of Visual Studio, a helper batch file has been provided to assist with
-	this. Please run `build-openssl -help` for usage details.
+	As OpenSSL does not support side-by-side compilation when using different
+	versions of Visual Studio, a helper batch file has been provided to assist
+	with this. Please run `build-openssl -help` for usage details.

	## Building with Visual C++

-	To build with VC++, you will of course have to first install VC++ which is
-	part of Visual Studio.
+	To build with VC++, you have to first install VC++ which is part of Visual
+	Studio.

	Once you have VC++ installed you should launch the application and open one of
	the solution or workspace files. The VC directory names are based on the
-	version of Visual C++ that you will be using. Each version of Visual Studio
-	has a default version of Visual C++. We offer these versions:
+	version of Visual C++ that you use. Each version of Visual Studio has a
+	default version of Visual C++. We offer these versions:

	- VC10 (Visual Studio 2010 Version 10.0)
	- VC11 (Visual Studio 2012 Version 11.0)
@@ -99,9 +99,9 @@ use `VC10\curl-all.sln` to build curl and libcurl.
	## Running DLL based configurations

	If you are a developer and plan to run the curl tool from Visual Studio with
-	any third-party libraries (such as OpenSSL or libssh2) then you will
-	need to add the search path of these DLLs to the configuration's PATH
-	environment. To do that:
+	any third-party libraries (such as OpenSSL or libssh2) then you need to add
+	the search path of these DLLs to the configuration's PATH environment. To do
+	that:

	1. Open the 'curl-all.sln' or 'curl.sln' solutions
	2. Right-click on the 'curl' project and select Properties
@@ -122,8 +122,8 @@ DLL Debug - DLL OpenSSL (x64):
	C:\Windows;C:\Windows\System32\Wbem

	If you are using a configuration that uses multiple third-party library DLLs
-	(such as DLL Debug - DLL OpenSSL - DLL libssh2) then 'Path to DLL' will need
-	to contain the path to both of these.
+	(such as DLL Debug - DLL OpenSSL - DLL libssh2) then 'Path to DLL' need to
+	contain the path to both of these.

	## Notes

@@ -139,14 +139,14 @@ Should you wish to help out with some of the items on the TODO list, or find
	bugs in the project files that need correcting, and would like to submit
	updated files back then please note that, whilst the solution files can be
	edited directly, the templates for the project files (which are stored in the
-	git repository) will need to be modified rather than the generated project
-	files that Visual Studio uses.
+	git repository) need to be modified rather than the generated project files
+	that Visual Studio uses.

	## Legacy Windows and SSL

	Some of the project configurations use Schannel (Windows SSPI), the native SSL
	library that comes with the Windows OS. Schannel in Windows 8 and earlier is
	not able to connect to servers that no longer support the legacy handshakes
-	and algorithms used by those versions. If you will be using curl in one of
-	those earlier versions of Windows you should choose another SSL backend like
+	and algorithms used by those versions. If you are using curl in one of those
+	earlier versions of Windows you should choose another SSL backend like
	OpenSSL.

src/tool_vms.c+1 -1

@@ -84,7 +84,7 @@ int is_vms_shell(void)
	* feature macro settings, and one of the exit routines is hidden at compile
	* time.
	*
-	* Since we want Curl to work properly under the VMS DCL shell and Unix
+	* Since we want curl to work properly under the VMS DCL shell and Unix
	* shells under VMS, this routine should compile correctly regardless of
	* the settings.
	*/

tests/CI.md+2 -2

@@ -6,7 +6,7 @@ SPDX-License-Identifier: curl

	# Continuous Integration for curl

-	Curl runs in many different environments, so every change is run against a
+	curl runs in many different environments, so every change is run against a
	large number of test suites.

	Every pull request is verified for each of the following:
@@ -58,7 +58,7 @@ GitHub Actions runs the following tests:
	- macOS tests with a variety of different compilation options
	- Fuzz tests ([see the curl-fuzzer repo for more
	info](https://github.com/curl/curl-fuzzer)).
-	- Curl compiled using the Rust TLS backend with Hyper
+	- curl compiled using the Rust TLS backend with Hyper

	These are each configured in different files in `.github/workflows`.

tests/http/README.md+33 -12

@@ -10,7 +10,9 @@ This is an additional test suite using a combination of Apache httpd and nghttpx

	# Usage

-	The test cases and necessary files are in `tests/http`. You can invoke `pytest` from there or from the top level curl checkout and it will find all tests.
+	The test cases and necessary files are in `tests/http`. You can invoke
+	`pytest` from there or from the top level curl checkout and it finds all
+	tests.

	```
	curl> pytest test/http
@@ -29,16 +31,18 @@ curl/tests/http> pytest -vv -k test_01_02

	runs all test cases that have `test_01_02` in their name. This does not have to be the start of the name.

-	Depending on your setup, some test cases may be skipped and appear as `s` in the output. If you run pytest verbose, it will also give you the reason for skipping.
+	Depending on your setup, some test cases may be skipped and appear as `s` in
+	the output. If you run pytest verbose, it also gives you the reason for
+	skipping.

	# Prerequisites

-	You will need:
+	You need:

	1. a recent Python, the `cryptography` module and, of course, `pytest`
-	2. an apache httpd development version. On Debian/Ubuntu, the package `apache2-dev` has this.
+	2. an apache httpd development version. On Debian/Ubuntu, the package `apache2-dev` has this
	3. a local `curl` project build
-	3. optionally, a `nghttpx` with HTTP/3 enabled or h3 test cases will be skipped.
+	3. optionally, a `nghttpx` with HTTP/3 enabled or h3 test cases are skipped

	### Configuration

@@ -85,12 +89,23 @@ There is a lot of [`pytest` documentation](https://docs.pytest.org/) with exampl

	In `conftest.py` 3 "fixtures" are defined that are used by all test cases:

-	1. `env`: the test environment. It is an instance of class `testenv/env.py:Env`. It holds all information about paths, availability of features (HTTP/3), port numbers to use, domains and SSL certificates for those.
-	2. `httpd`: the Apache httpd instance, configured and started, then stopped at the end of the test suite. It has sites configured for the domains from `env`. It also loads a local module `mod_curltest?` and makes it available in certain locations. (more on mod_curltest below).
-	3. `nghttpx`: an instance of nghttpx that provides HTTP/3 support. `nghttpx` proxies those requests to the `httpd` server. In a direct mapping, so you may access all the resources under the same path as with HTTP/2. Only the port number used for HTTP/3 requests will be different.
-
-	`pytest` manages these fixture so that they are created once and terminated before exit. This means you can `Ctrl-C` a running pytest and the server will shutdown. Only when you brutally chop its head off, might there be servers left
-	behind.
+	1. `env`: the test environment. It is an instance of class
+	`testenv/env.py:Env`. It holds all information about paths, availability of
+	features (HTTP/3), port numbers to use, domains and SSL certificates for
+	those.
+	2. `httpd`: the Apache httpd instance, configured and started, then stopped at
+	the end of the test suite. It has sites configured for the domains from
+	`env`. It also loads a local module `mod_curltest?` and makes it available
+	in certain locations. (more on mod_curltest below).
+	3. `nghttpx`: an instance of nghttpx that provides HTTP/3 support. `nghttpx`
+	proxies those requests to the `httpd` server. In a direct mapping, so you
+	may access all the resources under the same path as with HTTP/2. Only the
+	port number used for HTTP/3 requests are different.
+
+	`pytest` manages these fixture so that they are created once and terminated
+	before exit. This means you can `Ctrl-C` a running pytest and the server then
+	shutdowns. Only when you brutally chop its head off, might there be servers
+	left behind.

	### Test Cases

@@ -126,4 +141,10 @@ The module adds 2 "handlers" to the Apache server (right now). Handler are piece
	* `s`: seconds (the default)
	* `ms`: milliseconds

-	As you can see, `mod_curltest`'s tweak handler allow to simulate many kinds of responses. An example of its use is `test_03_01` where responses are delayed using `chunk_delay`. This gives the response a defined duration and the test uses that to reload `httpd` in the middle of the first request. A graceful reload in httpd lets ongoing requests finish, but will close the connection afterwards and tear down the serving process. The following request need then to open a new connection. This is verified by the test case.
+	As you can see, `mod_curltest`'s tweak handler allow to simulate many kinds of
+	responses. An example of its use is `test_03_01` where responses are delayed
+	using `chunk_delay`. This gives the response a defined duration and the test
+	uses that to reload `httpd` in the middle of the first request. A graceful
+	reload in httpd lets ongoing requests finish, but closes the connection
+	afterwards and tears down the serving process. The following request then
+	needs to open a new connection. This is verified by the test case.

tests/libtest/lib1531.c+2 -2

@@ -46,7 +46,7 @@ CURLcode test(char *URL)

	global_init(CURL_GLOBAL_ALL);

-	/* Allocate one CURL handle per transfer */
+	/* Allocate one curl handle per transfer */
	easy = curl_easy_init();

	/* init a multi stack */
@@ -152,7 +152,7 @@ CURLcode test(char *URL)
	test_cleanup:
	curl_multi_cleanup(multi_handle);

-	/* Free the CURL handles */
+	/* Free the curl handles */
	curl_easy_cleanup(easy);
	curl_global_cleanup();

tests/unit/README.md+6 -6

@@ -12,9 +12,9 @@ big and complicated, we should split them into smaller and testable ones.
	## Build Unit Tests

	`./configure --enable-debug` is required for the unit tests to build. To
-	enable unit tests, there will be a separate static libcurl built that will be
-	used exclusively for linking unit test programs. Just build everything as
-	normal, and then you can run the unit test cases as well.
+	enable unit tests, there is a separate static libcurl built that is used
+	exclusively for linking unit test programs. Just build everything as normal,
+	and then you can run the unit test cases as well.

	## Run Unit Tests

@@ -25,8 +25,8 @@ can `cd tests` and `make` and then invoke individual unit tests with

	## Debug Unit Tests

-	If a specific test fails you will get told. The test case then has output left
-	in the %LOGDIR subdirectory, but most importantly you can re-run the test again
+	If a specific test fails you get told. The test case then has output left in
+	the %LOGDIR subdirectory, but most importantly you can re-run the test again
	using gdb by doing `./runtests.pl -g NNNN`. That is, add a `-g` to make it
	start up gdb and run the same case using that.

@@ -37,7 +37,7 @@ source file. The source file should be named `unitNNNN.c` where `NNNN` is a
	previously unused number.

	Add your test to `tests/unit/Makefile.inc` (if it is a unit test). Add your
-	test data file name to `tests/data/Makefile.am`
+	test data filename to `tests/data/Makefile.am`

	You also need a separate file called `tests/data/testNNNN` (using the same
	number) that describes your test case. See the test1300 file for inspiration

winbuild/README.md+26 -27

@@ -7,10 +7,9 @@ SPDX-License-Identifier: curl
	# Building curl with Visual C++

	This document describes how to compile, build and install curl and libcurl
-	from sources using the Visual C++ build tool. To build with VC++, you will of
-	course have to first install VC++. The minimum required version of VC is 6
-	(part of Visual Studio 6). However using a more recent version is strongly
-	recommended.
+	from sources using the Visual C++ build tool. To build with VC++, you have to
+	first install VC++. The minimum required version of VC is 6 (part of Visual
+	Studio 6). However using a more recent version is strongly recommended.

	VC++ is also part of the Windows Platform SDK. You do not have to install the
	full Visual Studio or Visual C++ if all you want is to build curl.
@@ -21,8 +20,8 @@ SPDX-License-Identifier: curl

	## Prerequisites

-	If you wish to support zlib, OpenSSL, c-ares, ssh2, you will have to download
-	them separately and copy them to the `deps` directory as shown below:
+	If you wish to support zlib, OpenSSL, c-ares, ssh2, you have to download them
+	separately and copy them to the `deps` directory as shown below:

	somedirectory\
	\|_curl-src
@@ -62,14 +61,14 @@ Open a Visual Studio Command prompt:

	## Build in the console

-	Once you are in the console, go to the winbuild directory in the Curl
+	Once you are in the console, go to the winbuild directory in the curl
	sources:

	cd curl-src\winbuild

	Then you can call `nmake /f Makefile.vc` with the desired options (see
-	below). The builds will be in the top src directory, `builds\` directory, in
-	a directory named using the options given to the nmake call.
+	below). The builds are in the top src directory, `builds\` directory, in a
+	directory named using the options given to the nmake call.

	nmake /f Makefile.vc mode=<static or dll> <options>

@@ -124,12 +123,12 @@ where `<options>` is one or many of:

	## Static linking of Microsoft's C runtime (CRT):

-	If you are using mode=static nmake will create and link to the static build
-	of libcurl but not the static CRT. If you must you can force nmake to link
-	in the static CRT by passing `RTLIBCFG=static`. Typically you shouldn't use
-	that option, and nmake will default to the DLL CRT. `RTLIBCFG` is rarely used
-	and therefore rarely tested. When passing `RTLIBCFG` for a configuration that
-	was already built but not with that option, or if the option was specified
+	If you are using mode=static, nmake creates and links to the static build of
+	libcurl but not the static CRT. If you must you can force nmake to link in
+	the static CRT by passing `RTLIBCFG=static`. Typically you shouldn't use that
+	option, and nmake defaults to the DLL CRT. `RTLIBCFG` is rarely used and
+	therefore rarely tested. When passing `RTLIBCFG` for a configuration that was
+	already built but not with that option, or if the option was specified
	differently, you must destroy the build directory containing the
	configuration so that nmake can build it from scratch.

@@ -139,17 +138,17 @@ where `<options>` is one or many of:

	## Building your own application with libcurl (Visual Studio example)

-	When you build curl and libcurl, nmake will show the relative path where the
-	output directory is. The output directory is named from the options nmake used
-	when building. You may also see temp directories of the same name but with
-	suffixes -obj-curl and -obj-lib.
+	When you build curl and libcurl, nmake shows the relative path where the
+	output directory is. The output directory is named from the options nmake
+	used when building. You may also see temp directories of the same name but
+	with suffixes -obj-curl and -obj-lib.

-	For example let's say you've built curl.exe and libcurl.dll from the Visual
+	For example let's say you have built curl.exe and libcurl.dll from the Visual
	Studio 2010 x64 Win64 Command Prompt:

	nmake /f Makefile.vc mode=dll VC=10

-	The output directory will have a name similar to
+	The output directory has a name similar to
	`..\builds\libcurl-vc10-x64-release-dll-ipv6-sspi-schannel`.

	The output directory contains subdirectories bin, lib and include. Those are
@@ -177,14 +176,14 @@ where `<options>` is one or many of:
	need to make a separate x86 build of libcurl.

	If you build libcurl static (`mode=static`) or debug (`DEBUG=yes`) then the
-	library name will vary and separate builds may be necessary for separate
+	library name varies and separate builds may be necessary for separate
	configurations of your project within the same platform. This is discussed in
	the next section.

	## Building your own application with a static libcurl

	When building an application that uses the static libcurl library on Windows,
-	you must define `CURL_STATICLIB`. Otherwise the linker will look for dynamic
+	you must define `CURL_STATICLIB`. Otherwise the linker looks for dynamic
	import symbols.

	The static library name has an `_a` suffix in the basename and the debug
@@ -201,8 +200,8 @@ where `<options>` is one or many of:
	## Legacy Windows and SSL

	When you build curl using the build files in this directory the default SSL
-	backend will be Schannel (Windows SSPI), the native SSL library that comes
-	with the Windows OS. Schannel in Windows 8 and earlier is not able to connect
-	to servers that no longer support the legacy handshakes and algorithms used by
-	those versions. If you will be using curl in one of those earlier versions of
+	backend is Schannel (Windows SSPI), the native SSL library that comes with
+	the Windows OS. Schannel in Windows 8 and earlier is not able to connect to
+	servers that no longer support the legacy handshakes and algorithms used by
+	those versions. If you are using curl in one of those earlier versions of
	Windows you should choose another SSL backend like OpenSSL.