← Commit list

92efb3db7e

Daniel Stenberg

2021-11-01

SUCCESS Duration: 120s

Subject

docs: reduce use of "very"

Binary

Download Binary (721 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 92efb3db7e172946a467d6303f982f282c1d001f
Previous HEAD position was d52316e460 tests/smbserver.py: fix compatibility with impacket 0.9.23+
HEAD is now at 92efb3db7e docs: reduce use of "very"

$ git clean -fdx
Removing Makefile
Removing Makefile.in
Removing aclocal.m4
Removing autom4te.cache/
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/curl.1
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/curl_config.h
Removing lib/curl_config.h.in
Removing lib/curl_ctype.o
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-bufref.lo
Removing lib/libcurl_la-bufref.o
Removing lib/libcurl_la-c-hyper.lo
Removing lib/libcurl_la-c-hyper.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_ctype.lo
Removing lib/libcurl_la-curl_ctype.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_ntlm_wb.lo
Removing lib/libcurl_la-curl_ntlm_wb.o
Removing lib/libcurl_la-curl_path.lo
Removing lib/libcurl_la-curl_path.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_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-dict.lo
Removing lib/libcurl_la-dict.o
Removing lib/libcurl_la-doh.lo
Removing lib/libcurl_la-doh.o
Removing lib/libcurl_la-dotdot.lo
Removing lib/libcurl_la-dotdot.o
Removing lib/libcurl_la-dynbuf.lo
Removing lib/libcurl_la-dynbuf.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-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-hmac.lo
Removing lib/libcurl_la-hmac.o
Removing lib/libcurl_la-hostasyn.lo
Removing lib/libcurl_la-hostasyn.o
Removing lib/libcurl_la-hostcheck.lo
Removing lib/libcurl_la-hostcheck.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-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_win32.lo
Removing lib/libcurl_la-idn_win32.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-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-non-ascii.lo
Removing lib/libcurl_la-non-ascii.o
Removing lib/libcurl_la-nonblock.lo
Removing lib/libcurl_la-nonblock.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-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-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-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-wildcard.lo
Removing lib/libcurl_la-wildcard.o
Removing lib/libcurl_la-x509asn1.lo
Removing lib/libcurl_la-x509asn1.o
Removing lib/nonblock.o
Removing lib/stamp-h1
Removing lib/strtoofft.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-ngtcp2.lo
Removing lib/vquic/libcurl_la-ngtcp2.o
Removing lib/vquic/libcurl_la-quiche.lo
Removing lib/vquic/libcurl_la-quiche.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-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-gskit.lo
Removing lib/vtls/libcurl_la-gskit.o
Removing lib/vtls/libcurl_la-gtls.lo
Removing lib/vtls/libcurl_la-gtls.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-mesalink.lo
Removing lib/vtls/libcurl_la-mesalink.o
Removing lib/vtls/libcurl_la-nss.lo
Removing lib/vtls/libcurl_la-nss.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-wolfssl.lo
Removing lib/vtls/libcurl_la-wolfssl.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/tool_binmode.o
Removing src/tool_bname.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_wrt.o
Removing src/tool_cfgable.o
Removing src/tool_convert.o
Removing src/tool_dirhie.o
Removing src/tool_doswin.o
Removing src/tool_easysrc.o
Removing src/tool_filetime.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_homedir.o
Removing src/tool_hugehelp.c
Removing src/tool_hugehelp.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_panykey.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_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 test-driver
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/configurehelp.pm
Removing tests/data/Makefile
Removing tests/data/Makefile.in
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:120: installing './compile'
configure.ac:293: installing './config.guess'
configure.ac:293: installing './config.sub'
configure.ac:120: installing './install-sh'
configure.ac:125: installing './missing'
docs/examples/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'

$ 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 ECH support... no
checking for path separator... :
checking for sed... /usr/bin/sed
checking for grep... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
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 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... 7.80.0-DEV
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 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 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 inline... inline
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 if compiler is LCC... no
checking if compiler is SGI MIPSpro C... no
checking if compiler is SGI MIPS C... no
checking if compiler is SunPro C... no
checking if compiler is Tiny C... no
checking if compiler is Watcom C... 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 -Wenum-conversion
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 for windows.h... no
checking whether build target is a native Windows one... no
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 link macOS CoreFoundation and SystemConfiguration framework... no
checking to see if the compiler supports __builtin_available()... no
checking whether to support http... yes
checking whether to support ftp... yes
checking whether to support file... 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 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 for windows.h... (cached) no
checking for winsock2.h... (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 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 ldapssl.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)... no
checking for library containing psl_builtin... -lpsl
checking for library containing gsasl_init... no
checking for RTMP_Init in -lrtmp... no
checking whether versioned symbols are wanted... no
checking whether to enable Windows native IDN (Windows native builds only)... 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 pkg-config... (cached) /usr/bin/pkg-config
checking for libngtcp2 options with pkg-config... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for fish options with pkg-config... no
checking for malloc.h... yes
checking for memory.h... 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 sys/uio.h... yes
checking for assert.h... yes
checking for unistd.h... (cached) yes
checking for stdlib.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 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 alloca.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 socket.h... no
checking for sys/resource.h... yes
checking for libgen.h... yes
checking for locale.h... yes
checking for errno.h... yes
checking for stdbool.h... yes
checking for arpa/tftp.h... yes
checking for sys/filio.h... no
checking for sys/wait.h... yes
checking for setjmp.h... yes
checking for an ANSI C-conforming const... yes
checking for compiler support of C99 variadic macro style... yes
checking for compiler support of old gcc variadic macro style... 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 short... 2
checking size of time_t... 8
checking size of off_t... 8
checking size of curl_off_t... 8
checking for long long... yes
checking if numberLL works... 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 sys/types.h... (cached) yes
checking for poll.h... (cached) yes
checking for sys/poll.h... (cached) yes
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 types of args and return type for select... int,fd_set *,struct timeval *,int
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for recv... yes
checking types of args and return type for recv... int,void *,size_t,int,ssize_t
checking for sys/types.h... (cached) yes
checking for sys/socket.h... (cached) yes
checking for send... yes
checking types of args and return type for send... int,const void *,size_t,int,ssize_t
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 string.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 for sys/types.h... (cached) yes
checking for socket.h... (cached) no
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 if connect can be linked... yes
checking if connect is prototyped... yes
checking if connect is compilable... yes
checking if connect usage allowed... yes
checking if connect might be used... yes
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 for windows.h... (cached) no
checking for winsock2.h... (cached) no
checking for ws2tcpip.h... (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 for stdlib.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 can be linked... yes
checking if gethostbyname is prototyped... yes
checking if gethostbyname is compilable... yes
checking if gethostbyname usage allowed... yes
checking if gethostbyname might be used... 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 net/if.h... (cached) yes
checking if if_nametoindex can be linked... yes
checking if if_nametoindex is prototyped... yes
checking if if_nametoindex is compilable... yes
checking if if_nametoindex usage allowed... yes
checking if if_nametoindex 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 localtime_r can be linked... yes
checking if localtime_r is prototyped... yes
checking if localtime_r is compilable... yes
checking if localtime_r seems to work... yes
checking if localtime_r usage allowed... yes
checking if localtime_r might be used... yes
checking if memrchr can be linked... yes
checking if memrchr is prototyped... no
checking if memrchr might be used... no
checking if poll can be linked... yes
checking if poll is prototyped... yes
checking if poll is compilable... yes
checking if poll seems to work... yes
checking if poll usage allowed... yes
checking if poll might be used... yes
checking if setsockopt can be linked... yes
checking if setsockopt is prototyped... yes
checking if setsockopt is compilable... yes
checking if setsockopt usage allowed... yes
checking if setsockopt might be used... yes
checking if setsockopt SO_NONBLOCK is compilable... no
checking if setsockopt SO_NONBLOCK might be used... no
checking for sys/types.h... (cached) yes
checking for signal.h... 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 for setjmp.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 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 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... no
checking if strerror_r is POSIX 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 stricmp can be linked... no
checking if stricmp might be used... no
checking if strncmpi can be linked... no
checking if strncmpi might be used... no
checking if strnicmp can be linked... no
checking if strnicmp might be used... no
checking if strstr can be linked... yes
checking if strstr is prototyped... yes
checking if strstr is compilable... yes
checking if strstr usage allowed... yes
checking if strstr 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 sys/types.h... (cached) yes
checking for sys/uio.h... (cached) yes
checking if writev can be linked... yes
checking if writev is prototyped... yes
checking if writev is compilable... yes
checking if writev usage allowed... yes
checking if writev might be used... yes
checking for ccache gcc options needed to detect all undeclared functions... none needed
checking whether getpwuid_r is declared... yes
checking for fnmatch... yes
checking for geteuid... yes
checking for getpass_r... no
checking deeper for getpass_r... but still 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 deeper for mach_absolute_time... but still no
checking for pipe... yes
checking for setlocale... yes
checking for setmode... no
checking deeper for setmode... but still no
checking for setrlimit... yes
checking for usleep... yes
checking for utime... yes
checking for utimes... yes
checking how to set a socket into non-blocking mode... fcntl O_NONBLOCK
checking for perl... /usr/bin/perl
checking for gnroff... no
checking for nroff... /usr/bin/nroff
checking how to use *nroff to get plain text from man pages... -man
checking whether to enable the threaded resolver... yes
checking whether to use POSIX threads for threaded resolver... auto
checking for pthread.h... yes
checking for pthread_create... 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 cryptographic authentication methods... yes
checking whether to support NTLM... yes
checking whether to enable NTLM delegation to winbind's helper... no
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 date parsing... yes
checking whether to support netrc parsing... yes
checking whether to support progress-meter... yes
checking whether to support DNS shuffling... yes
checking whether to support curl_easy_option*... yes
checking whether to support alt-svc... no
configure: disables HSTS due to lack of SSL
checking whether hiding of library internal symbols will actually happen... yes
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/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 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: amending lib/Makefile
configure: amending src/Makefile
configure: amending tests/unit/Makefile
configure: amending tests/server/Makefile
configure: amending tests/libtest/Makefile
configure: amending docs/examples/Makefile
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 -Wenum-conversion
CPPFLAGS:
LDFLAGS:
LIBS: -lpsl -lz

curl version: 7.80.0-DEV
SSL: no (--with-{openssl,gnutls,nss,mbedtls,wolfssl,schannel,secure-transport,mesalink,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 libcurl: Shared=no, Static=yes
Built-in manual: enabled
--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 fallback:
LDAP: no (--enable-ldap / --with-ldap-lib / --with-lber-lib)
LDAPS: no (--enable-ldaps)
RTSP: enabled
RTMP: no (--with-librtmp)
PSL: enabled
Alt-svc: enabled (--disable-alt-svc)
HSTS: no (--enable-hsts)
HTTP1: enabled (internal)
HTTP2: no (--with-nghttp2, --with-hyper)
HTTP3: no (--with-ngtcp2, --with-quiche)
ECH: no (--enable-ech)
Protocols: DICT FILE FTP GOPHER HTTP IMAP MQTT POP3 RTSP SMTP TELNET TFTP
Features: AsynchDNS IPv6 Largefile PSL UnixSockets alt-svc libz

configure: WARNING: Cannot find libraries for LDAP support: LDAP disabled
configure: WARNING: SSL disabled, you will not be able to use HTTPS, FTPS, NTLM and more.
configure: WARNING: Use --with-openssl, --with-gnutls, --with-wolfssl, --with-mbedtls, --with-nss, --with-schannel, --with-secure-transport, --with-mesalink, --with-amissl, --with-bearssl or --with-rustls to address this.
configure: WARNING: libgsasl was not found
configure: WARNING: Cannot find libraries for IDN support: IDN disabled

$ 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-altsvc.lo
CC libcurl_la-amigaos.lo
CC libcurl_la-asyn-ares.lo
CC libcurl_la-asyn-thread.lo
CC libcurl_la-base64.lo
CC libcurl_la-bufref.lo
CC libcurl_la-c-hyper.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_ctype.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_ntlm_wb.lo
CC libcurl_la-curl_path.lo
CC libcurl_la-curl_range.lo
CC libcurl_la-curl_rtmp.lo
CC libcurl_la-curl_sasl.lo
CC libcurl_la-curl_sspi.lo
CC libcurl_la-curl_threads.lo
CC libcurl_la-dict.lo
CC libcurl_la-doh.lo
CC libcurl_la-dotdot.lo
CC libcurl_la-dynbuf.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-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-hmac.lo
CC libcurl_la-hostasyn.lo
CC libcurl_la-hostcheck.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-http2.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-http_aws_sigv4.lo
CC libcurl_la-idn_win32.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-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-non-ascii.lo
CC libcurl_la-nonblock.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-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-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-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-wildcard.lo
CC libcurl_la-x509asn1.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-gskit.lo
CC vtls/libcurl_la-gtls.lo
CC vtls/libcurl_la-keylog.lo
CC vtls/libcurl_la-mbedtls.lo
CC vtls/libcurl_la-mbedtls_threadlock.lo
CC vtls/libcurl_la-mesalink.lo
CC vtls/libcurl_la-nss.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 vquic/libcurl_la-ngtcp2.lo
CC vquic/libcurl_la-quiche.lo
CC vquic/libcurl_la-vquic.lo
CC vssh/libcurl_la-libssh.lo
CC vssh/libcurl_la-libssh2.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 src
make[1]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/src'
Making all in ../docs
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
Making all in .
make[3]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
if test "..x" != "..x" -a -e "./curl.1"; then \
/usr/bin/install -c -m 644 "./curl.1" /root/asi_db/builds/curl/_worktrees/w0/docs/curl.1; fi
cd cmdline-opts && make
make[4]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
generate ../../docs/curl.1
make[4]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
make[3]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
Making all in cmdline-opts
make[3]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs/cmdline-opts'
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/docs'
make[2]: Entering directory '/root/asi_db/builds/curl/_worktrees/w0/src'
CC slist_wc.o
CC tool_binmode.o
CC tool_bname.o
CC tool_cb_dbg.o
CC tool_cb_hdr.o
CC tool_cb_prg.o
CC tool_cb_rea.o
CC tool_cb_wrt.o
CC tool_cb_see.o
CC tool_cfgable.o
CC tool_convert.o
CC tool_dirhie.o
CC tool_easysrc.o
CC tool_doswin.o
CC tool_filetime.o
CC tool_formparse.o
CC tool_getparam.o
CC tool_getpass.o
CC tool_help.o
CC tool_helpers.o
CC tool_homedir.o
HUGE tool_hugehelp.c
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_panykey.o
CC tool_paramhlp.o
CC tool_parsecfg.o
CC tool_progress.o
CC tool_strdup.o
CC tool_setopt.o
CC tool_sleep.o
CC tool_urlglob.o
CC tool_util.o
CC tool_vms.o
CC tool_writeout.o
CC tool_writeout_json.o
CC tool_xattr.o
CC ../lib/strtoofft.o
CC ../lib/nonblock.o
CC ../lib/warnless.o
CC ../lib/curl_ctype.o
CC ../lib/curl_multibyte.o
CC ../lib/version_win32.o
CC ../lib/dynbuf.o
CC tool_hugehelp.o
CCLD curl
make[2]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/src'
make[1]: Leaving directory '/root/asi_db/builds/curl/_worktrees/w0/src'
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 →

docs/CODE_REVIEW.md+3 -3

@@ -36,9 +36,9 @@ Changing the API and the ABI may be fine in a change but it needs to be done
	deliberately and carefully. If not, a reviewer must help the author to realize
	the mistake.

-	curl and libcurl are similarly very strict on not modifying existing
-	behavior. API and ABI stability is not enough, the behavior should also remain
-	intact as far as possible.
+	curl and libcurl are similarly strict on not modifying existing behavior. API
+	and ABI stability is not enough, the behavior should also remain intact as far
+	as possible.

	## Code style

docs/CODE_STYLE.md+5 -5

@@ -2,7 +2,7 @@

	Source code that has a common style is easier to read than code that uses
	different styles in different places. It helps making the code feel like one
-	single code base. Easy-to-read is a very important property of code and helps
+	single code base. Easy-to-read is an important property of code and helps
	making it easier to review when new things are added and it helps debugging
	code when developers are trying to figure out why things go wrong. A unified
	style is more important than individual contributors having their own personal
@@ -56,10 +56,10 @@ introduced in the C standard until C99. We use only __/* comments */__.
	## Long lines

	Source code in curl may never be wider than 79 columns and there are two
-	reasons for maintaining this even in the modern era of very large and high
+	reasons for maintaining this even in the modern era of large and high
	resolution screens:

-	1. Narrower columns are easier to read than very wide ones. There's a reason
+	1. Narrower columns are easier to read than wide ones. There's a reason
	newspapers have used columns for decades or centuries.

	2. Narrower columns allow developers to easier show multiple pieces of code
@@ -154,8 +154,8 @@ if(!ptr)

	## New block on a new line

-	We never write multiple statements on the same source line, even for very
-	short if() conditions.
+	We never write multiple statements on the same source line, even for short
+	if() conditions.

	```c
	if(a)

docs/CONTRIBUTE.md+11 -11

@@ -96,9 +96,9 @@ and regression in the future.
	### Patch Against Recent Sources

	Please try to get the latest available sources to make your patches against.
-	It makes the lives of the developers so much easier. The very best is if you
-	get the most up-to-date sources from the git repository, but the latest
-	release archive is quite OK as well!
+	It makes the lives of the developers so much easier. The best is if you get
+	the most up-to-date sources from the git repository, but the latest release
+	archive is quite OK as well!

	### Documentation

@@ -120,8 +120,8 @@ in the test suite. Every feature that is added should get at least one valid
	test case that verifies that it works as documented. If every submitter also
	posts a few test cases, it won't end up as a heavy burden on a single person!

-	If you don't have test cases or perhaps you have done something that is very
-	hard to write tests for, do explain exactly how you have otherwise tested and
+	If you don't have test cases or perhaps you have done something that is hard
+	to write tests for, do explain exactly how you have otherwise tested and
	verified your changes.

	## Sharing Your Changes
@@ -139,9 +139,9 @@ risks stalling and eventually just getting deleted without action. As a
	submitter of a change, you are the owner of that change until it has been merged.

	Respond on the list or on github about the change and answer questions and/or
-	fix nits/flaws. This is very important. We will take lack of replies as a
-	sign that you're not very anxious to get your patch accepted and we tend to
-	simply drop such changes.
+	fix nits/flaws. This is important. We will take lack of replies as a sign that
+	you're not anxious to get your patch accepted and we tend to simply drop such
+	changes.

	### About pull requests

@@ -242,9 +242,9 @@ you commit

	### Write Access to git Repository

-	If you are a very frequent contributor, you may be given push access to the
-	git repository and then you'll be able to push your changes straight into the
-	git repo instead of sending changes as pull requests or by mail as patches.
+	If you are a frequent contributor, you may be given push access to the git
+	repository and then you'll be able to push your changes straight into the git
+	repo instead of sending changes as pull requests or by mail as patches.

	Just ask if this is what you'd want. You will be required to have posted
	several high quality patches first, before you can be granted push access.

docs/FAQ+15 -15

@@ -215,15 +215,15 @@ FAQ
	another tool that uses libcurl.

	We do not add things to curl that other small and available tools already do
-	very well at the side. curl's output can be piped into another program or
+	well at the side. curl's output can be piped into another program or
	redirected to another file for the next program to interpret.

	We focus on protocol related issues and improvements. If you want to do more
-	magic with the supported protocols than curl currently does, chances are good
-	we will agree. If you want to add more protocols, we may very well agree.
+	magic with the supported protocols than curl currently does, chances are
+	good we will agree. If you want to add more protocols, we may agree.

	If you want someone else to do all the work while you wait for us to
-	implement it for you, that is not a very friendly attitude. We spend a
+	implement it for you, that is not a friendly attitude. We spend a
	considerable time already on maintaining and developing curl. In order to
	get more out of us, you should consider trading in some of your time and
	effort in return. Simply go to the GitHub repo which resides at
@@ -407,14 +407,14 @@ FAQ
	The reason why static libraries is much harder to deal with is that for them
	we don't get any help but the script itself must know or check what more
	libraries that are needed (with shared libraries, that dependency "chain" is
-	handled automatically). This is a very error-prone process and one that also
+	handled automatically). This is a error-prone process and one that also
	tends to vary over time depending on the release versions of the involved
	components and may also differ between operating systems.

-	For that reason, configure does very little attempts to actually figure this
-	out and you are instead encouraged to set LIBS and LDFLAGS accordingly when
-	you invoke configure, and point out the needed libraries and set the
-	necessary flags yourself.
+	For that reason, configure does few attempts to actually figure this out and
+	you are instead encouraged to set LIBS and LDFLAGS accordingly when you
+	invoke configure, and point out the needed libraries and set the necessary
+	flags yourself.

	2.2 Does curl work with other SSL libraries?

@@ -878,7 +878,7 @@ FAQ

	Also note that regular HTTP (using Basic authentication) and FTP passwords
	are sent as cleartext across the network. All it takes for anyone to fetch
-	them is to listen on the network. Eavesdropping is very easy. Use more secure
+	them is to listen on the network. Eavesdropping is easy. Use more secure
	authentication methods (like Digest, Negotiate or even NTLM) or consider the
	SSL-based alternatives HTTPS and FTPS.

@@ -988,7 +988,7 @@ FAQ
	4.16 My HTTP POST or PUT requests are slow!

	libcurl makes all POST and PUT requests (except for POST requests with a
-	very tiny request body) use the "Expect: 100-continue" header. This header
+	tiny request body) use the "Expect: 100-continue" header. This header
	allows the server to deny the operation early so that libcurl can bail out
	before having to send any data. This is useful in authentication
	cases and others.
@@ -1392,10 +1392,10 @@ FAQ

	6. License Issues

-	curl and libcurl are released under a MIT/X derivative license. The license is
-	very liberal and should not impose a problem for your project. This section
-	is just a brief summary for the cases we get the most questions. (Parts of
-	this section was much enhanced by Bjorn Reese.)
+	curl and libcurl are released under a MIT/X derivative license. The license
+	is liberal and should not impose a problem for your project. This section is
+	just a brief summary for the cases we get the most questions. (Parts of this
+	section was much enhanced by Bjorn Reese.)

	We are not lawyers and this is not legal advice. You should probably consult
	one if you want true and accurate legal insights without our prejudice. Note

docs/HELP-US.md+1 -1

@@ -19,7 +19,7 @@ down and report the bug. Or make your first pull request with a fix for that.

	Some projects mark small issues as "beginner friendly", "bite-sized" or
	similar. We don't do that in curl since such issues never linger around long
-	enough. Simple issues get handled very fast.
+	enough. Simple issues get handled fast.

	If you're looking for a smaller or simpler task in the project to help out
	with as an entry-point into the project, perhaps because you are a newcomer or

docs/HTTP-COOKIES.md+1 -1

@@ -14,7 +14,7 @@
	Cookies are set to the client with the Set-Cookie: header and are sent to
	servers with the Cookie: header.

-	For a very long time, the only spec explaining how to use cookies was the
+	For a long time, the only spec explaining how to use cookies was the
	original [Netscape spec from 1994](https://curl.se/rfc/cookie_spec.html).

	In 2011, [RFC6265](https://www.ietf.org/rfc/rfc6265.txt) was finally

docs/INTERNALS.md+3 -4

@@ -467,7 +467,7 @@ Return Codes and Informationals

	I've made things simple. Almost every function in libcurl returns a CURLcode,
	that must be `CURLE_OK` if everything is OK or otherwise a suitable error
-	code as the `curl/curl.h` include file defines. The very spot that detects an
+	code as the `curl/curl.h` include file defines. The place that detects an
	error must use the `Curl_failf()` function to set the human-readable error
	description.

@@ -797,7 +797,7 @@ Track Down Memory Leaks
	tests/memanalyze.pl dump

	This now outputs a report on what resources that were allocated but never
-	freed etc. This report is very fine for posting to the list!
+	freed etc. This report is fine for posting to the list!

	If this doesn't produce any output, no leak was detected in libcurl. Then
	the leak is mostly likely to be in your code.
@@ -812,8 +812,7 @@ Track Down Memory Leaks

	1. The application can use whatever event system it likes as it gets info
	from libcurl about what file descriptors libcurl waits for what action
-	on. (The previous API returns `fd_sets` which is very
-	`select()`-centric).
+	on. (The previous API returns `fd_sets` which is `select()`-centric).

	2. When the application discovers action on a single socket, it calls
	libcurl and informs that there was action on this particular socket and

docs/KNOWN_BUGS+5 -5

@@ -288,7 +288,7 @@ problems may have been fixed or changed somewhat since this was written!
	get "good" random) so applications trying to avoid the init for
	performance reasons would do wrong anyway

-	D) never very carefully documented so all this mostly just happened to work
+	D) not documented carefully so all this mostly just happened to work
	for some users

	However, in spite of the problems with the feature, there were some users who
@@ -529,10 +529,10 @@ problems may have been fixed or changed somewhat since this was written!
	5.12 flaky Windows CI builds

	We run many CI builds for each commit and PR on github, and especially a
-	number of the Windows builds are very flaky. This means that we rarely get
-	all CI builds go green and complete without errors. This is very unfortunate
-	as it makes us sometimes miss actual build problems and it is surprising to
-	newcomers to the project who (rightfully) don't expect this.
+	number of the Windows builds are flaky. This means that we rarely get all CI
+	builds go green and complete without errors. This is unfortunate as it makes
+	us sometimes miss actual build problems and it is surprising to newcomers to
+	the project who (rightfully) don't expect this.

	See https://github.com/curl/curl/issues/6972

docs/MAIL-ETIQUETTE+11 -11

@@ -39,9 +39,9 @@ MAIL ETIQUETTE
	Each mailing list is targeted to a specific set of users and subjects,
	please use the one or the ones that suit you the most.

-	Each mailing list has hundreds up to thousands of readers, meaning that
-	each mail sent will be received and read by a very large number of people.
-	People from various cultures, regions, religions and continents.
+	Each mailing list has hundreds up to thousands of readers, meaning that each
+	mail sent will be received and read by a large number of people. People
+	from various cultures, regions, religions and continents.

	1.2 Netiquette

@@ -133,16 +133,16 @@ MAIL ETIQUETTE
	send the email, your post will just be silently discarded.

	If you posted for the first time to the mailing list, you first need to wait
-	for an administrator to allow your email to go through (moderated). This normally
-	happens very quickly but in case we're asleep, you may have to wait a few
-	hours.
+	for an administrator to allow your email to go through (moderated). This
+	normally happens quickly but in case we're asleep, you may have to wait a
+	few hours.

	Once your email goes through it is sent out to several hundred or even
-	thousands of recipients. Your email may cover an area that not that many people
-	know about or are interested in. Or possibly the person who knows about it
-	is on vacation or under a very heavy work load right now. You may have to wait
-	for a response and you should not expect to get a response at all, but
-	hopefully you get an answer within a couple of days.
+	thousands of recipients. Your email may cover an area that not that many
+	people know about or are interested in. Or possibly the person who knows
+	about it is on vacation or under a heavy work load right now. You may have
+	to wait for a response and you should not expect to get a response at all,
+	but hopefully you get an answer within a couple of days.

	You do yourself and all of us a service when you include as many details as
	possible already in your first email. Mention your operating system and

docs/MANUAL.md+13 -13

@@ -275,8 +275,8 @@ Store the HTTP headers in a separate file (headers.txt in the example):

	curl --dump-header headers.txt curl.se

-	Note that headers stored in a separate file can be very useful at a later time
-	if you want curl to use cookies sent by the server. More about that in the
+	Note that headers stored in a separate file can be useful at a later time if
+	you want curl to use cookies sent by the server. More about that in the
	cookies section.

	## POST (HTTP)
@@ -509,8 +509,8 @@ second for 1 minute, run:

	curl -Y 3000 -y 60 www.far-away-site.com

-	This can very well be used in combination with the overall time limit, so
-	that the above operation must be completed in whole within 30 minutes:
+	This can be used in combination with the overall time limit, so that the above
+	operation must be completed in whole within 30 minutes:

	curl -m 1800 -Y 3000 -y 60 www.far-away-site.com

@@ -583,9 +583,9 @@ tables etc:

	## Extra Headers

-	When using curl in your own very special programs, you may end up needing
-	to pass on your own custom headers when getting a web page. You can do
-	this by using the `-H` flag.
+	When using curl in your own programs, you may end up needing to pass on your
+	own custom headers when getting a web page. You can do this by using the `-H`
+	flag.

	Example, send the header `X-you-and-me: yes` to the server when getting a
	page:
@@ -608,8 +608,8 @@ directory at your ftp site, do:

	curl ftp://user:[email protected]/README

-	But if you want the README file from the root directory of that very same
-	site, you need to specify the absolute file name:
+	But if you want the README file from the root directory of that same site, you
+	need to specify the absolute file name:

	curl ftp://user:[email protected]//README

@@ -839,7 +839,7 @@ 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.

-	A very simple `.netrc` file could look something like:
+	A simple `.netrc` file could look something like:

	machine curl.se login iamdaniel password mysecret

@@ -869,9 +869,9 @@ curl ask for one and you already entered the real password to kinit/kauth.

	## TELNET

-	The curl telnet support is basic and very 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:
+	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:

	curl telnet://remote.server.com

docs/SECURITY-PROCESS.md+5 -5

@@ -99,11 +99,11 @@ This is a private mailing list for discussions on and about curl security
	issues.

	Who is on this list? There are a couple of criteria you must meet, and then we
-	might ask you to join the list or you can ask to join it. It really isn't very
-	formal. We basically only require that you have a long-term presence in the
-	curl project and you have shown an understanding for the project and its way
-	of working. You must've been around for a good while and you should have no
-	plans in vanishing in the near future.
+	might ask you to join the list or you can ask to join it. It really isn't a
+	formal process. We basically only require that you have a long-term presence
+	in the curl project and you have shown an understanding for the project and
+	its way of working. You must've been around for a good while and you should
+	have no plans in vanishing in the near future.

	We do not make the list of participants public mostly because it tends to vary
	somewhat over time and a list somewhere will only risk getting outdated.

docs/TODO+3 -3

@@ -832,7 +832,7 @@
	CURLOPT_PINNEDPUBLICKEY does not consider the hashes of intermediate & root
	certificates when comparing the pinned keys. Therefore it is not compatible
	with "HTTP Public Key Pinning" as there also intermediate and root
-	certificates can be pinned. This is very useful as it prevents webadmins from
+	certificates can be pinned. This is useful as it prevents webadmins from
	"locking themselves out of their servers".

	Adding this feature would make curls pinning 100% compatible to HPKP and
@@ -981,8 +981,8 @@
	18.6 Option to make -Z merge lined based outputs on stdout

	When a user requests multiple lined based files using -Z and sends them to
-	stdout, curl will not "merge" and send complete lines fine but may very well
-	send partial lines from several sources.
+	stdout, curl will not "merge" and send complete lines fine but may send
+	partial lines from several sources.

	https://github.com/curl/curl/issues/5175

docs/TheArtOfHttpScripting.md+16 -16

@@ -21,7 +21,7 @@

	## The HTTP Protocol

-	HTTP is the protocol used to fetch data from web servers. It is a very simple
+	HTTP is the protocol used to fetch data from web servers. It is a simple
	protocol that is built upon TCP/IP. The protocol also allows information to
	get sent to the server from the client using a few different methods, as will
	be shown here.
@@ -252,13 +252,13 @@
	your browser. That's generally a good thing when you want to be able to
	bookmark that page with your given data, but it is an obvious disadvantage if
	you entered secret information in one of the fields or if there are a large
-	amount of fields creating a very long and unreadable URL.
+	amount of fields creating a long and unreadable URL.

	The HTTP protocol then offers the POST method. This way the client sends the
	data separated from the URL and thus you won't see any of it in the URL
	address field.

-	The form would look very similar to the previous one:
+	The form would look similar to the previous one:

	```html
	<form method="POST" action="junk.cgi">
@@ -313,10 +313,10 @@

	## Hidden Fields

-	A very common way for HTML based applications to pass state information
-	between pages is to add hidden fields to the forms. Hidden fields are already
-	filled in, they aren't displayed to the user and they get passed along just
-	as all the other fields.
+	A common way for HTML based applications to pass state information between
+	pages is to add hidden fields to the forms. Hidden fields are already filled
+	in, they aren't displayed to the user and they get passed along just as all
+	the other fields.

	A similar example form with one visible field, one hidden field and one
	submit button could look like:
@@ -337,8 +337,8 @@
	## Figure Out What A POST Looks Like

	When you're about fill in a form and send to a server by using curl instead
-	of a browser, you're of course very interested in sending a POST exactly the
-	way your browser does.
+	of a browser, you're of course interested in sending a POST exactly the way
+	your browser does.

	An easy way to get to see this, is to save the HTML page with the form on
	your local disk, modify the 'method' to a GET, and press the submit button
@@ -408,9 +408,9 @@
	able to watch your passwords if you pass them as plain command line
	options. There are ways to circumvent this.

-	It is worth noting that while this is how HTTP Authentication works, very
-	many websites will not use this concept when they provide logins etc. See the
-	Web Login chapter further below for more details on that.
+	It is worth noting that while this is how HTTP Authentication works, many
+	websites will not use this concept when they provide logins etc. See the Web
+	Login chapter further below for more details on that.

	# More HTTP Headers

@@ -430,7 +430,7 @@

	## User Agent

-	Very similar to the referer field, all HTTP requests may set the User-Agent
+	Similar to the referer field, all HTTP requests may set the User-Agent
	field. It names what user agent (client) that is being used. Many
	applications use this information to decide how to display pages. Silly web
	programmers try to make different pages for users of different browsers to
@@ -690,9 +690,9 @@

	## Check what the browsers do

-	A very good helper to make sure you do this right, is the web browsers'
-	developers tools that let you view all headers you send and receive (even
-	when using HTTPS).
+	A good helper to make sure you do this right, is the web browsers' developers
+	tools that let you view all headers you send and receive (even when using
+	HTTPS).

	A more raw approach is to capture the HTTP traffic on the network with tools
	such as Wireshark or tcpdump and check what headers that were sent and

docs/URL-SYNTAX.md+2 -2

@@ -20,7 +20,7 @@ changes over time.
	URL parsers as implemented in browsers, libraries and tools usually opt to
	support one of the mentioned specifications. Bugs, differences in
	interpretations and the moving nature of the WHATWG spec does however make it
-	very unlikely that multiple parsers treat URLs the exact same way!
+	unlikely that multiple parsers treat URLs the exact same way!

	## Security

@@ -43,7 +43,7 @@ security concerns:
	1. If you have an application that runs as or in a server application, getting
	an unfiltered URL can trick your application to access a local resource
	instead of a remote resource. Protecting yourself against localhost accesses
-	is very hard when accepting user provided URLs.
+	is hard when accepting user provided URLs.

	2. Such custom URLs can access other ports than you planned as port numbers
	are part of the regular URL format. The combination of a local host and a

docs/cmdline-opts/cookie.d+3 -3

@@ -32,6 +32,6 @@ use the Netscape format.

	This option can be used multiple times.

-	Users very often want to both read cookies from a file and write updated
-	cookies back to a file, so using both --cookie and --cookie-jar in the same
-	command line is common.
+	Users often want to both read cookies from a file and write updated cookies
+	back to a file, so using both --cookie and --cookie-jar in the same command
+	line is common.

docs/cmdline-opts/ftp-method.d+1 -1

@@ -13,7 +13,7 @@ server. The method argument should be one of the following alternatives:
	.RS
	.IP multicwd
	curl does a single CWD operation for each path part in the given URL. For deep
-	hierarchies this means very many commands. This is how RFC 1738 says it should
+	hierarchies this means many commands. This is how RFC 1738 says it should
	be done. This is the default but the slowest behavior.
	.IP nocwd
	curl does no CWD at all. curl will do SIZE, RETR, STOR etc and give a full

docs/cmdline-opts/netrc-optional.d+1 -1

@@ -6,5 +6,5 @@ Category: curl
	Example: --netrc-optional $URL
	Added: 7.9.8
	---
-	Very similar to --netrc, but this option makes the .netrc usage optional
+	Similar to --netrc, but this option makes the .netrc usage optional
	and not mandatory as the --netrc option does.

docs/cmdline-opts/netrc.d+3 -3

@@ -13,8 +13,8 @@ complain if that file doesn't have the right permissions (it should be
	neither world- nor group-readable). The environment variable "HOME" is used
	to find the home directory.

-	A quick and very simple example of how to setup a .netrc to allow curl
-	to FTP to the machine host.domain.com with user name \&'myself' and password
-	\&'secret' should look similar to:
+	A quick and simple example of how to setup a .netrc to allow curl to FTP to
+	the machine host.domain.com with user name \&'myself' and password \&'secret'
+	should look similar to:

	.B "machine host.domain.com login myself password secret"

docs/cmdline-opts/trace-ascii.d+3 -3

@@ -10,9 +10,9 @@ Enables a full trace dump of all incoming and outgoing data, including
	descriptive information, to the given output file. Use "-" as filename to have
	the output sent to stdout.

-	This is very similar to --trace, but leaves out the hex part and only shows
-	the ASCII part of the dump. It makes smaller output that might be easier to
-	read for untrained humans.
+	This is similar to --trace, but leaves out the hex part and only shows the
+	ASCII part of the dump. It makes smaller output that might be easier to read
+	for untrained humans.

	This option is global and does not need to be specified for each use of
	--next.

docs/cmdline-opts/user.d+2 -2

@@ -18,8 +18,8 @@ still.
	On systems where it works, curl will hide the given option argument from
	process listings. This is not enough to protect credentials from possibly
	getting seen by other users on the same system as they will still be visible
-	for a brief moment before cleared. Such sensitive data should be retrieved
-	from a file instead or similar and never used in clear text in a command line.
+	for a moment before cleared. Such sensitive data should be retrieved from a
+	file instead or similar and never used in clear text in a command line.

	When using Kerberos V5 with a Windows based server you should include the
	Windows domain name in the user name, in order for the server to successfully

docs/libcurl/curl_easy_pause.3+3 -3

@@ -99,9 +99,9 @@ If the downloaded data is compressed and is asked to get uncompressed
	automatically on download, libcurl will continue to uncompress the entire
	downloaded chunk and it will cache the data uncompressed. This has the side-
	effect that if you download something that is compressed a lot, it can result
-	in a very large data amount needing to be allocated to save the data during
-	the pause. This said, you should probably consider not using paused receiving
-	if you allow libcurl to uncompress data automatically.
+	in a large data amount needing to be allocated to save the data during the
+	pause. This said, you should probably consider not using paused receiving if
+	you allow libcurl to uncompress data automatically.
	.SH AVAILABILITY
	Added in 7.18.0.
	.SH RETURN VALUE

docs/libcurl/curl_easy_send.3+2 -2

@@ -73,8 +73,8 @@ sent was for internal SSL processing, and no other data could be sent.
	Added in 7.18.2.
	.SH RETURN VALUE
	On success, returns \fBCURLE_OK\fP and stores the number of bytes actually
-	sent into \fB*n\fP. Note that this may very well be less than the amount you
-	wanted to send.
+	sent into \fB*n\fP. Note that this may be less than the amount you wanted to
+	send.

	On failure, returns the appropriate error code.

docs/libcurl/curl_mime_data.3+1 -1

@@ -42,7 +42,7 @@ Setting a part's contents twice is valid: only the value set by the last call
	is retained. It is possible to unassign part's contents by setting
	\fIdata\fP to NULL.

-	Setting very large data is memory consuming: one might consider using
+	Setting large data is memory consuming: one might consider using
	\fIcurl_mime_data_cb(3)\fP in such a case.
	.SH EXAMPLE
	.nf

docs/libcurl/curl_multi_info_read.3+4 -4

@@ -48,10 +48,10 @@ is emptied.
	calling \fIcurl_multi_cleanup(3)\fP, \fIcurl_multi_remove_handle(3)\fP or
	\fIcurl_easy_cleanup(3)\fP.

-	The 'CURLMsg' struct is very simple and only contains very basic information.
-	If more involved information is wanted, the particular "easy handle" is
-	present in that struct and can be used in subsequent regular
-	\fIcurl_easy_getinfo(3)\fP calls (or similar):
+	The 'CURLMsg' struct is simple and only contains basic information. If more
+	involved information is wanted, the particular "easy handle" is present in
+	that struct and can be used in subsequent regular \fIcurl_easy_getinfo(3)\fP
+	calls (or similar):

	.nf
	struct CURLMsg {

docs/libcurl/curl_multi_perform.3+3 -3

@@ -46,9 +46,9 @@ is less than the amount of easy handles you've added to the multi handle), you
	know that there is one or more transfers less "running". You can then call
	\fIcurl_multi_info_read(3)\fP to get information about each individual
	completed transfer, and that returned info includes CURLcode and more. If an
-	added handle fails very quickly, it may never be counted as a running_handle.
-	You could use \fIcurl_multi_info_read(3)\fP to track actual status of the
-	added handles in that case.
+	added handle fails quickly, it may never be counted as a running_handle. You
+	could use \fIcurl_multi_info_read(3)\fP to track actual status of the added
+	handles in that case.

	When \fIrunning_handles\fP is set to zero (0) on the return of this function,
	there is no longer any transfers in progress.

docs/libcurl/curl_multi_timeout.3+2 -3

@@ -38,9 +38,8 @@ to CURL_SOCKET_TIMEOUT, or call \fIcurl_multi_perform(3)\fP if you're using
	the simpler and older multi interface approach.

	The timeout value returned in the long \fBtimeout\fP points to, is in number
-	of milliseconds at this very moment. If 0, it means you should proceed
-	immediately without waiting for anything. If it returns -1, there's no timeout
-	at all set.
+	of milliseconds at this moment. If 0, it means you should proceed immediately
+	without waiting for anything. If it returns -1, there's no timeout at all set.

	An application that uses the multi_socket API SHOULD NOT use this function, but
	SHOULD instead use \fIcurl_multi_setopt(3)\fP and its

docs/libcurl/libcurl-easy.3+4 -4

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -35,9 +35,9 @@ is available etc. \fIcurl_easy_setopt(3)\fP is used for all this.

	\fICURLOPT_URL(3)\fP is only option you really must set, as otherwise there
	can be no transfer. Another commonly used option is \fICURLOPT_VERBOSE(3)\fP
-	that will help you see what libcurl is doing under the hood, very useful when
-	debugging for example. The \fIcurl_easy_setopt(3)\fP man page has a full index
-	of the over 200 available options.
+	that will help you see what libcurl is doing under the hood, which is useful
+	when debugging for example. The \fIcurl_easy_setopt(3)\fP man page has a full
+	index of the over 200 available options.

	If you at any point would like to blank all previously set options for a
	single easy handle, you can call \fIcurl_easy_reset(3)\fP and you can also

docs/libcurl/libcurl-errors.3+4 -4

@@ -43,9 +43,9 @@ support. The support might be a compile-time option that you didn't use, it
	can be a misspelled protocol string or just a protocol libcurl has no code
	for.
	.IP "CURLE_FAILED_INIT (2)"
-	Very early initialization code failed. This is likely to be an internal error
-	or problem, or a resource problem where something fundamental couldn't get
-	done at init time.
+	Early initialization code failed. This is likely to be an internal error or
+	problem, or a resource problem where something fundamental couldn't get done
+	at init time.
	.IP "CURLE_URL_MALFORMAT (3)"
	The URL was not properly formatted.
	.IP "CURLE_NOT_BUILT_IN (4)"
@@ -365,4 +365,4 @@ There is no fragment part in the URL.
	.BR curl_easy_strerror "(3), " curl_multi_strerror "(3), "
	.BR curl_share_strerror "(3), " curl_url_strerror "(3), "
	.BR CURLOPT_ERRORBUFFER "(3), " CURLOPT_VERBOSE "(3), "
-	.BR CURLOPT_DEBUGFUNCTION "(3)"
+	.BR CURLOPT_DEBUGFUNCTION "(3)"

docs/libcurl/libcurl-security.3+11 -11

@@ -42,9 +42,9 @@ many of these and similar types of weaknesses of which application writers
	should be aware.
	.SH "Command Lines"
	If you use a command line tool (such as curl) that uses libcurl, and you give
-	options to the tool on the command line those options can very likely get read
-	by other users of your system when they use 'ps' or other tools to list
-	currently running processes.
+	options to the tool on the command line those options can get read by other
+	users of your system when they use 'ps' or other tools to list currently
+	running processes.

	To avoid these problems, never feed sensitive things to programs using command
	line options. Write them to a protected file and use the \-K option to avoid
@@ -64,11 +64,11 @@ To avoid these problems, don't use .netrc files and never store passwords in
	plain text anywhere.
	.SH "Clear Text Passwords"
	Many of the protocols libcurl supports send name and password unencrypted as
-	clear text (HTTP Basic authentication, FTP, TELNET etc). It is very easy for
-	anyone on your network or a network nearby yours to just fire up a network
-	analyzer tool and eavesdrop on your passwords. Don't let the fact that HTTP
-	Basic uses base64 encoded passwords fool you. They may not look readable at a
-	first glance, but they very easily "deciphered" by anyone within seconds.
+	clear text (HTTP Basic authentication, FTP, TELNET etc). It is easy for anyone
+	on your network or a network nearby yours to just fire up a network analyzer
+	tool and eavesdrop on your passwords. Don't let the fact that HTTP Basic uses
+	base64 encoded passwords fool you. They may not look readable at a first
+	glance, but they are easily "deciphered" by anyone within seconds.

	To avoid this problem, use an authentication mechanism or other protocol that
	doesn't let snoopers see your password: Digest, CRAM-MD5, Kerberos, SPNEGO or
@@ -315,8 +315,8 @@ The fact that FTP uses two connections makes it vulnerable in a way that is
	hard to avoid.
	.SH "Denial of Service"
	A malicious server could cause libcurl to effectively hang by sending data
-	very slowly, or even no data at all but just keeping the TCP connection open.
-	This could effectively result in a denial-of-service attack. The
+	slowly, or even no data at all but just keeping the TCP connection open. This
+	could effectively result in a denial-of-service attack. The
	\fICURLOPT_TIMEOUT(3)\fP and/or \fICURLOPT_LOW_SPEED_LIMIT(3)\fP options can
	be used to mitigate against this.

@@ -370,7 +370,7 @@ information with faked data.
	.SH "Setuid applications using libcurl"
	libcurl-using applications that set the 'setuid' bit to run with elevated or
	modified rights also implicitly give that extra power to libcurl and this
-	should only be done after very careful considerations.
+	should only be done after careful considerations.

	Giving setuid powers to the application means that libcurl can save files using
	those new rights (if for example the `SSLKEYLOGFILE` environment variable is

docs/libcurl/libcurl-thread.3+4 -4

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 2015 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 2015 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -84,9 +84,9 @@ threaded situation as there will be race where libcurl risks restoring the
	former signal handler while another thread should still ignore it.
	.IP "Name resolving"
	\fBgethostby* functions and other system calls.\fP These functions, provided
-	by your operating system, must be thread safe. It is very important that
-	libcurl can find and use thread safe versions of these and other system calls,
-	as otherwise it can't function fully thread safe. Some operating systems are
+	by your operating system, must be thread safe. It is important that libcurl
+	can find and use thread safe versions of these and other system calls, as
+	otherwise it can't function fully thread safe. Some operating systems are
	known to have faulty thread implementations. We have previously received
	problem reports on *BSD (at least in the past, they may be working fine these
	days). Some operating systems that are known to have solid and working thread

docs/libcurl/libcurl-tutorial.3+32 -34

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -86,9 +86,9 @@ The people behind libcurl have put a considerable effort to make libcurl work
	on a large amount of different operating systems and environments.

	You program libcurl the same way on all platforms that libcurl runs on. There
-	are only very few minor considerations that differ. If you just make sure to
-	write your code portable enough, you may very well create yourself a very
-	portable program. libcurl shouldn't stop you from that.
+	are only a few minor details that differ. If you just make sure to write your
+	code portable enough, you can create a portable program. libcurl shouldn't
+	stop you from that.

	.SH "Global Preparation"
	The program must initialize some of the libcurl functionality globally. That
@@ -120,7 +120,7 @@ libcurl has a default protection mechanism that detects if
	\fIcurl_global_init(3)\fP hasn't been called by the time
	\fIcurl_easy_perform(3)\fP is called and if that is the case, libcurl runs the
	function itself with a guessed bit pattern. Please note that depending solely
-	on this is not considered nice nor very good.
+	on this is not considered nice nor good.

	When the program no longer uses libcurl, it should call
	\fIcurl_global_cleanup(3)\fP, which is the opposite of the init call. It will
@@ -284,14 +284,13 @@ If \fICURLOPT_VERBOSE(3)\fP is not enough, you increase the level of debug
	data your application receive by using the \fICURLOPT_DEBUGFUNCTION(3)\fP.

	Getting some in-depth knowledge about the protocols involved is never wrong,
-	and if you're trying to do funny things, you might very well understand
-	libcurl and how to use it better if you study the appropriate RFC documents
-	at least briefly.
+	and if you're trying to do funny things, you might understand libcurl and how
+	to use it better if you study the appropriate RFC documents at least briefly.

	.SH "Upload Data to a Remote Site"
	libcurl tries to keep a protocol independent approach to most transfers, thus
-	uploading to a remote FTP site is very similar to uploading data to an HTTP
-	server with a PUT request.
+	uploading to a remote FTP site is similar to uploading data to an HTTP server
+	with a PUT request.

	Of course, first you either create an easy handle or you re-use one existing
	one. Then you set the URL to operate on just like before. This is the remote
@@ -373,7 +372,7 @@ curl use this file, use the \fICURLOPT_NETRC(3)\fP option:

	curl_easy_setopt(easyhandle, CURLOPT_NETRC, 1L);

-	And a very basic example of how such a .netrc file may look like:
+	And a basic example of how such a .netrc file may look like:

	.nf
	machine myhost.mydomain.com
@@ -795,10 +794,9 @@ For HTTP proxies: the fact that the proxy is an HTTP proxy puts certain
	restrictions on what can actually happen. A requested URL that might not be a
	HTTP URL will be still be passed to the HTTP proxy to deliver back to
	libcurl. This happens transparently, and an application may not need to
-	know. I say "may", because at times it is very important to understand that
-	all operations over an HTTP proxy use the HTTP protocol. For example, you
-	can't invoke your own custom FTP commands or even proper FTP directory
-	listings.
+	know. I say "may", because at times it is important to understand that all
+	operations over an HTTP proxy use the HTTP protocol. For example, you can't
+	invoke your own custom FTP commands or even proper FTP directory listings.

	.IP "Proxy Options"

@@ -863,7 +861,7 @@ remote host").

	Because of the nature of this operation, where the proxy has no idea what kind
	of data that is passed in and out through this tunnel, this breaks some of the
-	very few advantages that come from using a proxy, such as caching. Many
+	few advantages that come from using a proxy, such as caching. Many
	organizations prevent this kind of tunneling to other destination port numbers
	than 443 (which is the default HTTPS port number).

@@ -942,9 +940,9 @@ may also be added in the future.

	Each easy handle will attempt to keep the last few connections alive for a
	while in case they are to be used again. You can set the size of this "cache"
-	with the \fICURLOPT_MAXCONNECTS(3)\fP option. Default is 5. There is very
-	seldom any point in changing this value, and if you think of changing this it
-	is often just a matter of thinking again.
+	with the \fICURLOPT_MAXCONNECTS(3)\fP option. Default is 5. There is rarely
+	any point in changing this value, and if you think of changing this it is
+	often just a matter of thinking again.

	To force your upcoming request to not use an already existing connection (it
	will even close one first if there happens to be one alive to the same host
@@ -986,7 +984,7 @@ libcurl is your friend here too.
	.IP CUSTOMREQUEST
	If just changing the actual HTTP request keyword is what you want, like when
	GET, HEAD or POST is not good enough for you, \fICURLOPT_CUSTOMREQUEST(3)\fP
-	is there for you. It is very simple to use:
+	is there for you. It is simple to use:

	curl_easy_setopt(easyhandle, CURLOPT_CUSTOMREQUEST, "MYOWNREQUEST");

@@ -1045,9 +1043,9 @@ data size is unknown.
	.IP "HTTP Version"

	All HTTP requests includes the version number to tell the server which version
-	we support. libcurl speaks HTTP 1.1 by default. Some very old servers don't
-	like getting 1.1-requests and when dealing with stubborn old things like that,
-	you can tell libcurl to use 1.0 instead by doing something like this:
+	we support. libcurl speaks HTTP 1.1 by default. Some old servers don't like
+	getting 1.1-requests and when dealing with stubborn old things like that, you
+	can tell libcurl to use 1.0 instead by doing something like this:

	curl_easy_setopt(easyhandle, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_0);

@@ -1057,14 +1055,14 @@ Not all protocols are HTTP-like, and thus the above may not help you when
	you want to make, for example, your FTP transfers to behave differently.

	Sending custom commands to an FTP server means that you need to send the
-	commands exactly as the FTP server expects them (RFC959 is a good guide
-	here), and you can only use commands that work on the control-connection
-	alone. All kinds of commands that require data interchange and thus need
-	a data-connection must be left to libcurl's own judgement. Also be aware
-	that libcurl will do its very best to change directory to the target
-	directory before doing any transfer, so if you change directory (with CWD
-	or similar) you might confuse libcurl and then it might not attempt to
-	transfer the file in the correct remote directory.
+	commands exactly as the FTP server expects them (RFC959 is a good guide here),
+	and you can only use commands that work on the control-connection alone. All
+	kinds of commands that require data interchange and thus need a
+	data-connection must be left to libcurl's own judgement. Also be aware that
+	libcurl will do its best to change directory to the target directory before
+	doing any transfer, so if you change directory (with CWD or similar) you might
+	confuse libcurl and then it might not attempt to transfer the file in the
+	correct remote directory.

	A little example that deletes a given file before an operation:

@@ -1336,9 +1334,9 @@ with the particular file descriptors libcurl uses for the moment.
	When you then call select(), it'll return when one of the file handles signal
	action and you then call \fIcurl_multi_perform(3)\fP to allow libcurl to do
	what it wants to do. Take note that libcurl does also feature some time-out
-	code so we advise you to never use very long timeouts on select() before you
-	call \fIcurl_multi_perform(3)\fP again. \fIcurl_multi_timeout(3)\fP is
-	provided to help you get a suitable timeout period.
+	code so we advise you to never use long timeouts on select() before you call
+	\fIcurl_multi_perform(3)\fP again. \fIcurl_multi_timeout(3)\fP is provided to
+	help you get a suitable timeout period.

	Another precaution you should use: always call \fIcurl_multi_fdset(3)\fP
	immediately before the select() call since the current set of file descriptors

docs/libcurl/opts/CURLINFO_APPCONNECT_TIME.3+4 -4

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -30,9 +30,9 @@ CURLcode curl_easy_getinfo(CURL handle, CURLINFO_APPCONNECT_TIME, double timep
	.SH DESCRIPTION
	Pass a pointer to a double to receive the time, in seconds, it took from the
	start until the SSL/SSH connect/handshake to the remote host was completed.
-	This time is most often very near to the \fICURLINFO_PRETRANSFER_TIME(3)\fP
-	time, except for cases such as HTTP pipelining where the pretransfer time can
-	be delayed due to waits in line for the pipeline and more.
+	This time is most often close to the \fICURLINFO_PRETRANSFER_TIME(3)\fP time,
+	except for cases such as HTTP pipelining where the pretransfer time can be
+	delayed due to waits in line for the pipeline and more.

	When a redirect is followed, the time from each request is added together.

docs/libcurl/opts/CURLINFO_APPCONNECT_TIME_T.3+7 -7

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 2018 - 2019, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 2018 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -28,12 +28,12 @@ CURLINFO_APPCONNECT_TIME_T \- get the time until the SSL/SSH handshake is comple

	CURLcode curl_easy_getinfo(CURL handle, CURLINFO_APPCONNECT_TIME_T, curl_off_t timep);
	.SH DESCRIPTION
-	Pass a pointer to a curl_off_t to receive the time, in microseconds,
-	it took from the
-	start until the SSL/SSH connect/handshake to the remote host was completed.
-	This time is most often very near to the \fICURLINFO_PRETRANSFER_TIME_T(3)\fP
-	time, except for cases such as HTTP pipelining where the pretransfer time can
-	be delayed due to waits in line for the pipeline and more.
+	Pass a pointer to a curl_off_t to receive the time, in microseconds, it took
+	from the start until the SSL/SSH connect/handshake to the remote host was
+	completed. This time is most often close to the
+	\fICURLINFO_PRETRANSFER_TIME_T(3)\fP time, except for cases such as HTTP
+	pipelining where the pretransfer time can be delayed due to waits in line for
+	the pipeline and more.

	When a redirect is followed, the time from each request is added together.

docs/libcurl/opts/CURLINFO_EFFECTIVE_METHOD.3+3 -3

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -34,8 +34,8 @@ CURLcode curl_easy_getinfo(CURL *handle, CURLINFO_EFFECTIVE_METHOD,
	Pass in a pointer to a char pointer and get the last used effective HTTP
	method.

-	In cases when you've asked libcurl to follow redirects, the method may very
-	well not be the same method the first request would use.
+	In cases when you've asked libcurl to follow redirects, the method may not be
+	the same method the first request would use.

	The \fBmethodp\fP pointer will be NULL or pointing to private memory you MUST
	NOT free - it gets freed when you call \fIcurl_easy_cleanup(3)\fP on the

docs/libcurl/opts/CURLINFO_EFFECTIVE_URL.3+3 -3

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -30,8 +30,8 @@ CURLcode curl_easy_getinfo(CURL handle, CURLINFO_EFFECTIVE_URL, char *urlp);
	.SH DESCRIPTION
	Pass in a pointer to a char pointer and get the last used effective URL.

-	In cases when you've asked libcurl to follow redirects, it may very well not
-	be the same value you set with \fICURLOPT_URL(3)\fP.
+	In cases when you've asked libcurl to follow redirects, it may not be the same
+	value you set with \fICURLOPT_URL(3)\fP.

	The \fBurlp\fP pointer will be NULL or pointing to private memory you MUST NOT
	free - it gets freed when you call \fIcurl_easy_cleanup(3)\fP on the

docs/libcurl/opts/CURLINFO_REDIRECT_URL.3+4 -4

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -30,9 +30,9 @@ CURLcode curl_easy_getinfo(CURL handle, CURLINFO_REDIRECT_URL, char *urlp);
	.SH DESCRIPTION
	Pass a pointer to a char pointer to receive the URL a redirect \fIwould\fP
	take you to if you would enable \fICURLOPT_FOLLOWLOCATION(3)\fP. This can come
-	very handy if you think using the built-in libcurl redirect logic isn't good
-	enough for you but you would still prefer to avoid implementing all the magic
-	of figuring out the new URL.
+	handy if you think using the built-in libcurl redirect logic isn't good enough
+	for you but you would still prefer to avoid implementing all the magic of
+	figuring out the new URL.

	This URL is also set if the \fICURLOPT_MAXREDIRS(3)\fP limit prevented a
	redirect to happen (since 7.54.1).

docs/libcurl/opts/CURLOPT_CURLU.3+3 -3

@@ -36,9 +36,9 @@ CURLU *. Setting \fICURLOPT_CURLU(3)\fP will explicitly override
	transfer is started.

	libcurl will use this handle and its contents read-only and will not change
-	its contents. An application can very well update the contents of the URL
-	handle after a transfer is done and if the same handle is then used in a
-	subsequent request the updated contents will then be used.
+	its contents. An application can update the contents of the URL handle after a
+	transfer is done and if the same handle is then used in a subsequent request
+	the updated contents will then be used.
	.SH DEFAULT
	The default value of this parameter is NULL.
	.SH PROTOCOLS

docs/libcurl/opts/CURLOPT_DNS_CACHE_TIMEOUT.3+1 -1

@@ -52,7 +52,7 @@ CURL *curl = curl_easy_init();
	if(curl) {
	curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/foo.bin");

-	/* only reuse addresses for a very short time */
+	/* only reuse addresses for a short time */
	curl_easy_setopt(curl, CURLOPT_DNS_CACHE_TIMEOUT, 2L);

	ret = curl_easy_perform(curl);

docs/libcurl/opts/CURLOPT_ERRORBUFFER.3+3 -3

@@ -34,9 +34,9 @@ return code from \fIcurl_easy_perform(3)\fP and related functions. The buffer
	\fBmust be at least CURL_ERROR_SIZE bytes big\fP.

	You must keep the associated buffer available until libcurl no longer needs
-	it. Failing to do so will cause very odd behavior or even crashes. libcurl
-	will need it until you call \fIcurl_easy_cleanup(3)\fP or you set the same
-	option again to use a different pointer.
+	it. Failing to do so will cause odd behavior or even crashes. libcurl will
+	need it until you call \fIcurl_easy_cleanup(3)\fP or you set the same option
+	again to use a different pointer.

	Do not rely on the contents of the buffer unless an error code was returned.
	Since 7.60.0 libcurl will initialize the contents of the error buffer to an

docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.3+2 -2

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -51,7 +51,7 @@ dictates which request method it will use in the subsequent request: For 301,
	will make libcurl send the same method again.

	For users who think the existing location following is too naive, too simple
-	or just lacks features, it is very easy to instead implement your own redirect
+	or just lacks features, it is easy to instead implement your own redirect
	follow logic with the use of \fIcurl_easy_getinfo(3)\fP's
	\fICURLINFO_REDIRECT_URL(3)\fP option instead of using
	\fICURLOPT_FOLLOWLOCATION(3)\fP.

docs/libcurl/opts/CURLOPT_HEADERFUNCTION.3+5 -5

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -38,10 +38,10 @@ shown above.

	This function gets called by libcurl as soon as it has received header
	data. The header callback will be called once for each header and only
-	complete header lines are passed on to the callback. Parsing headers is very
-	easy using this. \fIbuffer\fP points to the delivered data, and the size of
-	that data is \fInitems\fP; \fIsize\fP is always 1. Do not assume that the
-	header line is null-terminated!
+	complete header lines are passed on to the callback. Parsing headers is easy
+	to do using this callback. \fIbuffer\fP points to the delivered data, and the
+	size of that data is \fInitems\fP; \fIsize\fP is always 1. Do not assume that
+	the header line is null-terminated!

	The pointer named \fIuserdata\fP is the one you set with the
	\fICURLOPT_HEADERDATA(3)\fP option.

docs/libcurl/opts/CURLOPT_HTTP200ALIASES.3+5 -5

@@ -32,11 +32,11 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_HTTP200ALIASES,
	.SH DESCRIPTION
	Pass a pointer to a linked list of \fIaliases\fP to be treated as valid HTTP
	200 responses. Some servers respond with a custom header response line. For
-	example, SHOUTcast servers respond with "ICY 200 OK". Also some very old
-	Icecast 1.3.x servers will respond like that for certain user agent headers or
-	in absence of such. By including this string in your list of aliases,
-	the response will be treated as a valid HTTP header line such as
-	"HTTP/1.0 200 OK".
+	example, SHOUTcast servers respond with "ICY 200 OK". Also some old Icecast
+	1.3.x servers will respond like that for certain user agent headers or in
+	absence of such. By including this string in your list of aliases, the
+	response will be treated as a valid HTTP header line such as "HTTP/1.0 200
+	OK".

	The linked list should be a fully valid list of struct curl_slist structs, and
	be properly filled in. Use \fIcurl_slist_append(3)\fP to create the list and

docs/libcurl/opts/CURLOPT_MAXAGE_CONN.3+2 -2

@@ -34,8 +34,8 @@ reuse for this request.

	The "connection cache" that holds previously used connections. When a new
	request is to be done, it will consider any connection that matches for
-	reuse. The \fICURLOPT_MAXAGE_CONN(3)\fP limit prevents libcurl from trying
-	very old connections for reuse, since old connections have a high risk of not
+	reuse. The \fICURLOPT_MAXAGE_CONN(3)\fP limit prevents libcurl from trying too
+	old connections for reuse, since old connections have a high risk of not
	working and thus trying them is a performance loss and sometimes service loss
	due to the difficulties to figure out the situation. If a connection is found
	in the cache that is older than this set \fImaxage\fP, it will instead be

docs/libcurl/opts/CURLOPT_MAXLIFETIME_CONN.3+1 -1

@@ -35,7 +35,7 @@ connection to have to be considered for reuse for this request.
	libcurl features a connection cache that holds previously used connections.
	When a new request is to be done, it will consider any connection that matches
	for reuse. The \fICURLOPT_MAXLIFETIME_CONN(3)\fP limit prevents libcurl from
-	trying very old connections for reuse. This can be used for client-side load
+	trying too old connections for reuse. This can be used for client-side load
	balancing. If a connection is found in the cache that is older than this set
	\fImaxlifetime\fP, it will instead be closed once any in-progress transfers
	complete.

docs/libcurl/opts/CURLOPT_PRE_PROXY.3+1 -1

@@ -59,7 +59,7 @@ Default is NULL, meaning no pre proxy is used.
	When you set a host name to use, do not assume that there's any particular
	single port number used widely for proxies. Specify it!
	.SH PROTOCOLS
-	All except file://. Note that some protocols don't do very well over proxy.
+	All except file://. Note that some protocols don't work well over proxy.
	.SH EXAMPLE
	.nf
	CURL *curl = curl_easy_init();

docs/libcurl/opts/CURLOPT_PROGRESSFUNCTION.3+1 -1

@@ -41,7 +41,7 @@ We encourage users to use the newer \fICURLOPT_XFERINFOFUNCTION(3)\fP instead,
	if you can.

	This function gets called by libcurl instead of its internal equivalent with a
-	frequent interval. While data is being transferred it will be called very
+	frequent interval. While data is being transferred it will be called
	frequently, and during slow periods like when nothing is being transferred it
	can slow down to about one call per second.

docs/libcurl/opts/CURLOPT_PROXY.3+1 -1

@@ -90,7 +90,7 @@ Default is NULL, meaning no proxy is used.
	When you set a host name to use, do not assume that there's any particular
	single port number used widely for proxies. Specify it!
	.SH PROTOCOLS
-	All except file://. Note that some protocols don't do very well over proxy.
+	All except file://. Note that some protocols don't work well over proxy.
	.SH EXAMPLE
	.nf
	CURL *curl = curl_easy_init();

docs/libcurl/opts/CURLOPT_PROXYTYPE.3+4 -4

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -36,9 +36,9 @@ HTTP Proxy. Default.
	.IP CURLPROXY_HTTPS
	HTTPS Proxy. (Added in 7.52.0 for OpenSSL, GnuTLS and NSS)
	.IP CURLPROXY_HTTP_1_0
-	HTTP 1.0 Proxy. This is very similar to CURLPROXY_HTTP except it uses HTTP/1.0
-	for any CONNECT tunnelling. It does not change the HTTP version of the actual
-	HTTP requests, controlled by \fICURLOPT_HTTP_VERSION(3)\fP.
+	HTTP 1.0 Proxy. This is similar to CURLPROXY_HTTP except it uses HTTP/1.0 for
+	any CONNECT tunnelling. It does not change the HTTP version of the actual HTTP
+	requests, controlled by \fICURLOPT_HTTP_VERSION(3)\fP.
	.IP CURLPROXY_SOCKS4
	SOCKS4 Proxy.
	.IP CURLPROXY_SOCKS4A

docs/libcurl/opts/CURLOPT_URL.3+3 -3

@@ -5,7 +5,7 @@
	.\" * \| (__\| \|_\| \| _ <\| \|___
	.\" * \___\|\___/\|_\| \_\_____\|
	.\" *
-	.\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <[email protected]>, et al.
+	.\" * Copyright (C) 1998 - 2021, Daniel Stenberg, <[email protected]>, et al.
	.\" *
	.\" * This software is licensed as described in the file COPYING, which
	.\" * you should have received as part of this distribution. The terms
@@ -88,8 +88,8 @@ security concerns:

	If you have an application that runs as or in a server application, getting an
	unfiltered URL can easily trick your application to access a local resource
-	instead of a remote. Protecting yourself against localhost accesses is very
-	hard when accepting user provided URLs.
+	instead of a remote. Protecting yourself against localhost accesses is hard
+	when accepting user provided URLs.

	Such custom URLs can also access other ports than you planned as port numbers
	are part of the regular URL format. The combination of a local host and a

docs/libcurl/opts/CURLOPT_VERBOSE.3+1 -1

@@ -29,7 +29,7 @@ CURLOPT_VERBOSE \- verbose mode
	CURLcode curl_easy_setopt(CURL *handle, CURLOPT_VERBOSE, long onoff);
	.SH DESCRIPTION
	Set the \fIonoff\fP parameter to 1 to make the library display a lot of
-	verbose information about its operations on this \fIhandle\fP. Very useful for
+	verbose information about its operations on this \fIhandle\fP. Useful for
	libcurl and/or protocol debugging and understanding. The verbose information
	will be sent to stderr, or the stream set with \fICURLOPT_STDERR(3)\fP.

docs/libcurl/opts/CURLOPT_XFERINFOFUNCTION.3+1 -1

@@ -38,7 +38,7 @@ Pass a pointer to your callback function, which should match the prototype
	shown above.

	This function gets called by libcurl instead of its internal equivalent with a
-	frequent interval. While data is being transferred it will be called very
+	frequent interval. While data is being transferred it will be called
	frequently, and during slow periods like when nothing is being transferred it
	can slow down to about one call per second.