← Commit list

d3d8773b14

Daniel Stenberg

2020-09-18

SUCCESS Duration: 113s

Subject

docs/TheArtOfHttpScripting: convert to markdown

Binary

Download Binary (682 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 d3d8773b142b77ea01c7fe16a3e80ee20d6ae4a3
Previous HEAD position was 559ed3ca25 docs/RESOURCES: remove
HEAD is now at d3d8773b14 docs/TheArtOfHttpScripting: convert to markdown

$ 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-curl_ctype.o
Removing lib/curl-curl_multibyte.o
Removing lib/curl-dynbuf.o
Removing lib/curl-nonblock.o
Removing lib/curl-strtoofft.o
Removing lib/curl-version_win32.o
Removing lib/curl-warnless.o
Removing lib/curl_config.h
Removing lib/curl_config.h.in
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-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-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_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-security.lo
Removing lib/libcurl_la-security.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/stamp-h1
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-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/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-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 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/curl-slist_wc.o
Removing src/curl-tool_binmode.o
Removing src/curl-tool_bname.o
Removing src/curl-tool_cb_dbg.o
Removing src/curl-tool_cb_hdr.o
Removing src/curl-tool_cb_prg.o
Removing src/curl-tool_cb_rea.o
Removing src/curl-tool_cb_see.o
Removing src/curl-tool_cb_wrt.o
Removing src/curl-tool_cfgable.o
Removing src/curl-tool_convert.o
Removing src/curl-tool_dirhie.o
Removing src/curl-tool_doswin.o
Removing src/curl-tool_easysrc.o
Removing src/curl-tool_filetime.o
Removing src/curl-tool_formparse.o
Removing src/curl-tool_getparam.o
Removing src/curl-tool_getpass.o
Removing src/curl-tool_help.o
Removing src/curl-tool_helpers.o
Removing src/curl-tool_homedir.o
Removing src/curl-tool_hugehelp.o
Removing src/curl-tool_libinfo.o
Removing src/curl-tool_main.o
Removing src/curl-tool_metalink.o
Removing src/curl-tool_msgs.o
Removing src/curl-tool_operate.o
Removing src/curl-tool_operhlp.o
Removing src/curl-tool_panykey.o
Removing src/curl-tool_paramhlp.o
Removing src/curl-tool_parsecfg.o
Removing src/curl-tool_progress.o
Removing src/curl-tool_setopt.o
Removing src/curl-tool_sleep.o
Removing src/curl-tool_strdup.o
Removing src/curl-tool_urlglob.o
Removing src/curl-tool_util.o
Removing src/curl-tool_vms.o
Removing src/curl-tool_writeout.o
Removing src/curl-tool_writeout_json.o
Removing src/curl-tool_xattr.o
Removing src/tool_hugehelp.c
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:44: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:44: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:147: CURL_CHECK_OPTION_DEBUG is expanded from...
configure.ac:44: the top level
configure.ac:45: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:45: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:181: CURL_CHECK_OPTION_OPTIMIZE is expanded from...
configure.ac:45: the top level
configure.ac:46: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:46: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:360: CURL_CHECK_OPTION_WARNINGS is expanded from...
configure.ac:46: the top level
configure.ac:47: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:47: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:394: CURL_CHECK_OPTION_WERROR is expanded from...
configure.ac:47: the top level
configure.ac:48: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:48: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:94: CURL_CHECK_OPTION_CURLDEBUG is expanded from...
configure.ac:48: the top level
configure.ac:49: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:49: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:237: CURL_CHECK_OPTION_SYMBOL_HIDING is expanded from...
configure.ac:49: the top level
configure.ac:50: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:50: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:58: CURL_CHECK_OPTION_ARES is expanded from...
configure.ac:50: the top level
configure.ac:51: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:51: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:328: CURL_CHECK_OPTION_RT is expanded from...
configure.ac:51: the top level
configure.ac:52: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:52: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:658: CURL_CHECK_OPTION_ESNI is expanded from...
configure.ac:52: the top level
configure.ac:123: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:123: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-functions.m4:7304: CURL_COVERAGE is expanded from...
configure.ac:123: the top level
configure.ac:376: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:376: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:376: the top level
configure.ac:377: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:377: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:377: the top level
configure.ac:395: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:395: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:395: the top level
configure.ac:396: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:396: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:396: the top level
configure.ac:410: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:410: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:410: the top level
configure.ac:411: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:411: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:411: the top level
configure.ac:425: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:425: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:425: the top level
configure.ac:426: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:426: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:426: the top level
configure.ac:441: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:441: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:441: the top level
configure.ac:442: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:442: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:442: the top level
configure.ac:473: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:473: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:473: the top level
configure.ac:474: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:474: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:474: the top level
configure.ac:499: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:499: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:499: the top level
configure.ac:500: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:500: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:500: the top level
configure.ac:515: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:515: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:515: the top level
configure.ac:516: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:516: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:516: the top level
configure.ac:530: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:530: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:530: the top level
configure.ac:531: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:531: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:531: the top level
configure.ac:545: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:545: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:545: the top level
configure.ac:546: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:546: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:546: the top level
configure.ac:561: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:561: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:561: the top level
configure.ac:562: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:562: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:562: the top level
configure.ac:578: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:578: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:578: the top level
configure.ac:579: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:579: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:579: the top level
configure.ac:595: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:595: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:595: the top level
configure.ac:596: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:596: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:596: the top level
configure.ac:611: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:611: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:611: the top level
configure.ac:612: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:612: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:612: the top level
configure.ac:627: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:627: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:627: the top level
configure.ac:628: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:628: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:628: the top level
configure.ac:643: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:643: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:643: the top level
configure.ac:644: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:644: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:644: the top level
configure.ac:663: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:663: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:663: the top level
configure.ac:664: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:664: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:664: the top level
configure.ac:684: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:684: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:684: the top level
configure.ac:685: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:685: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:685: the top level
configure.ac:704: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:704: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:704: the top level
configure.ac:911: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:911: You should run autoupdate.
./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from...
acinclude.m4:1575: CURL_CHECK_FUNC_CLOCK_GETTIME_MONOTONIC is expanded from...
acinclude.m4:1618: CURL_CHECK_LIBS_CLOCK_GETTIME_MONOTONIC is expanded from...
configure.ac:911: the top level
configure.ac:932: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:932: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:932: the top level
configure.ac:933: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:933: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:933: the top level
configure.ac:1039: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1039: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1039: the top level
configure.ac:1040: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1040: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1040: the top level
configure.ac:1125: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1125: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1125: the top level
configure.ac:1126: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1126: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1126: the top level
configure.ac:1211: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1211: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1211: the top level
configure.ac:1216: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1216: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1216: the top level
configure.ac:1297: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1297: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1297: the top level
configure.ac:1298: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1298: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1298: the top level
configure.ac:1309: warning: The macro `AC_TRY_RUN' is obsolete.
configure.ac:1309: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
configure.ac:1309: the top level
configure.ac:1347: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.ac:1347: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.ac:1347: the top level
configure.ac:1408: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1408: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1408: the top level
configure.ac:1415: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1415: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1415: the top level
configure.ac:1422: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1422: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1422: the top level
configure.ac:1588: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1588: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1588: the top level
configure.ac:1589: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1589: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1589: the top level
configure.ac:1615: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1615: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1615: the top level
configure.ac:1616: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1616: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1616: the top level
configure.ac:1620: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1620: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1620: the top level
configure.ac:1621: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1621: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1621: the top level
configure.ac:1650: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1650: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1650: the top level
configure.ac:1651: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1651: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1651: the top level
configure.ac:1655: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1655: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1655: the top level
configure.ac:1656: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1656: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1656: the top level
configure.ac:1680: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1680: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1680: the top level
configure.ac:1681: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1681: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1681: the top level
configure.ac:1716: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1716: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1716: the top level
configure.ac:1717: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:1717: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:1717: the top level
configure.ac:1735: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:1735: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.ac:1735: the top level
configure.ac:1827: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:1827: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
configure.ac:1827: the top level
configure.ac:1827: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:1827: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2894: _AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2911: AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from...
configure.ac:1827: the top level
configure.ac:2043: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2043: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2043: the top level
configure.ac:2054: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2054: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2054: the top level
configure.ac:2089: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2089: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2089: the top level
configure.ac:2090: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2090: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2090: the top level
configure.ac:2106: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2106: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2106: the top level
configure.ac:2107: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2107: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2107: the top level
configure.ac:2267: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2267: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2267: the top level
configure.ac:2268: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2268: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2268: the top level
configure.ac:2361: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2361: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2361: the top level
configure.ac:2362: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2362: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2362: the top level
configure.ac:2521: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2521: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2521: the top level
configure.ac:2522: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2522: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2522: the top level
configure.ac:2612: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2612: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2612: the top level
configure.ac:2613: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2613: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2613: the top level
configure.ac:2703: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2703: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2703: the top level
configure.ac:2704: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2704: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2704: the top level
configure.ac:2869: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2869: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
acinclude.m4:2163: CURL_CHECK_CA_BUNDLE is expanded from...
configure.ac:2869: the top level
configure.ac:2900: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2900: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2900: the top level
configure.ac:2901: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2901: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2901: the top level
configure.ac:2994: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2994: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2994: the top level
configure.ac:2995: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:2995: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:2995: the top level
configure.ac:3001: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3001: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3001: the top level
configure.ac:3002: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3002: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3002: the top level
configure.ac:3007: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3007: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3007: the top level
configure.ac:3008: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3008: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3008: the top level
configure.ac:3188: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3188: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3188: the top level
configure.ac:3189: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3189: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3189: the top level
configure.ac:3267: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3267: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3267: the top level
configure.ac:3268: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3268: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3268: the top level
configure.ac:3319: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3319: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3319: the top level
configure.ac:3320: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3320: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3320: the top level
configure.ac:3397: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3397: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3397: the top level
configure.ac:3398: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3398: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3398: the top level
configure.ac:3532: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3532: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3532: the top level
configure.ac:3533: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3533: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3533: the top level
configure.ac:3619: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3619: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3619: the top level
configure.ac:3620: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3620: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3620: the top level
configure.ac:3818: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3818: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3818: the top level
configure.ac:3819: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3819: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3819: the top level
configure.ac:3909: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3909: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3909: the top level
configure.ac:3910: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3910: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3910: the top level
configure.ac:3993: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3993: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3993: the top level
configure.ac:3994: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:3994: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:3994: the top level
configure.ac:4018: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4018: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4018: the top level
configure.ac:4019: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4019: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4019: the top level
configure.ac:4047: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:4047: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:4047: the top level
configure.ac:4134: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:4134: You should run autoupdate.
./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from...
configure.ac:4134: the top level
configure.ac:4249: warning: The macro `AC_TYPE_SIGNAL' is obsolete.
configure.ac:4249: You should run autoupdate.
./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from...
configure.ac:4249: the top level
configure.ac:4429: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4429: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:32: CURL_CHECK_OPTION_THREADED_RESOLVER is expanded from...
configure.ac:4429: the top level
configure.ac:4437: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4437: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4437: the top level
configure.ac:4439: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4439: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4439: the top level
configure.ac:4538: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4538: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4538: the top level
configure.ac:4539: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4539: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4539: the top level
configure.ac:4557: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4557: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4557: the top level
configure.ac:4558: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4558: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4558: the top level
configure.ac:4593: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4593: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4593: the top level
configure.ac:4594: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4594: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4594: the top level
configure.ac:4607: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4607: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/curl-confopts.m4:599: CURL_CHECK_OPTION_NTLM_WB is expanded from...
configure.ac:4607: the top level
configure.ac:4616: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4616: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4616: the top level
configure.ac:4617: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4617: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4617: the top level
configure.ac:4642: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4642: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4642: the top level
configure.ac:4643: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4643: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4643: the top level
configure.ac:4675: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4675: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4675: the top level
configure.ac:4676: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4676: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4676: the top level
configure.ac:4693: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4693: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4693: the top level
configure.ac:4694: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4694: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4694: the top level
configure.ac:4711: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4711: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4711: the top level
configure.ac:4712: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4712: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4712: the top level
configure.ac:4729: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4729: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4729: the top level
configure.ac:4730: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4730: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4730: the top level
configure.ac:4747: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4747: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4747: the top level
configure.ac:4748: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4748: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4748: the top level
configure.ac:4765: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4765: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4765: the top level
configure.ac:4766: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4766: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4766: the top level
configure.ac:4783: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4783: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4783: the top level
configure.ac:4784: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4784: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4784: the top level
configure.ac:4801: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4801: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4801: the top level
configure.ac:4802: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4802: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4802: the top level
configure.ac:4819: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4819: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4819: the top level
configure.ac:4820: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4820: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4820: the top level
configure.ac:4837: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4837: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4837: the top level
configure.ac:4838: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4838: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4838: the top level
configure.ac:4856: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4856: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4856: the top level
configure.ac:4857: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:4857: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:4857: the top level
configure.ac:120: installing './compile'
configure.ac:180: installing './config.guess'
configure.ac:180: 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 ESNI 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.73.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 sys/time.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 accepts debug disabling options... yes
configure: compiler options added: 
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 for good-to-use Mac CFLAGS... 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 winsock.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... (cached) yes
checking for 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 (Windows native builds only)... 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 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 quiche options with pkg-config... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for fish options with pkg-config... no
checking for egrep... (cached) /usr/bin/grep -E
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 sgtty.h... yes
checking for fcntl.h... yes
checking for alloca.h... yes
checking for time.h... (cached) 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 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 signal.h... yes
checking for sig_atomic_t... yes
checking if sig_atomic_t is already defined as volatile... no
checking return type of signal handlers... void
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/socket.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for ifaddrs.h... yes
checking if freeifaddrs can be linked... yes
checking if freeifaddrs is prototyped... yes
checking if freeifaddrs is compilable... yes
checking if freeifaddrs usage allowed... yes
checking if freeifaddrs 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 gai_strerror can be linked... yes
checking if gai_strerror is prototyped... yes
checking if gai_strerror is compilable... yes
checking if gai_strerror usage allowed... yes
checking if gai_strerror might be used... yes
checking if gethostbyaddr can be linked... yes
checking if gethostbyaddr is prototyped... yes
checking if gethostbyaddr is compilable... yes
checking if gethostbyaddr usage allowed... yes
checking if gethostbyaddr might be used... yes
checking if gethostbyaddr_r can be linked... yes
checking if gethostbyaddr_r is prototyped... yes
checking if gethostbyaddr_r takes 5 args.... no
checking if gethostbyaddr_r takes 7 args.... no
checking if gethostbyaddr_r takes 8 args.... yes
checking if gethostbyaddr_r is compilable... yes
checking if gethostbyaddr_r usage allowed... yes
checking if gethostbyaddr_r might be used... 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 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 if getservbyport_r can be linked... yes
checking if getservbyport_r is prototyped... yes
checking if getservbyport_r takes 4 args.... no
checking if getservbyport_r takes 5 args.... no
checking if getservbyport_r takes 6 args.... yes
checking if getservbyport_r is compilable... yes
checking if getservbyport_r usage allowed... yes
checking if getservbyport_r might be used... yes
checking for sys/types.h... (cached) yes
checking for sys/time.h... (cached) yes
checking for 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_ntoa_r can be linked... no
checking if inet_ntoa_r might be used... no
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... (cached) yes
checking if sigaction can be linked... yes
checking if sigaction is prototyped... yes
checking if sigaction is compilable... yes
checking if sigaction usage allowed... yes
checking if sigaction might be used... yes
checking if siginterrupt can be linked... yes
checking if siginterrupt is prototyped... yes
checking if siginterrupt is compilable... yes
checking if siginterrupt usage allowed... yes
checking if siginterrupt might be used... yes
checking if signal can be linked... yes
checking if signal is prototyped... yes
checking if signal is compilable... yes
checking if signal usage allowed... yes
checking if signal might be used... yes
checking for sys/types.h... (cached) yes
checking 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 strncasecmp can be linked... yes
checking if strncasecmp is prototyped... yes
checking if strncasecmp is compilable... yes
checking if strncasecmp usage allowed... yes
checking if strncasecmp might be used... yes
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 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
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.73.0-DEV
  SSL:              no      (--with-{ssl,gnutls,nss,mbedtls,wolfssl,schannel,secure-transport,mesalink,amissl,bearssl} )
  SSH:              no      (--with-{libssh,libssh2})
  zlib:             enabled
  brotli:           no      (--with-brotli)
  zstd:             no      (--with-zstd)
  GSS-API:          no      (--with-gssapi)
  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)
  Metalink:         no      (--with-libmetalink)
  PSL:              enabled
  Alt-svc:          no      (--enable-alt-svc)
  HTTP2:            disabled (--with-nghttp2)
  HTTP3:            disabled (--with-ngtcp2, --with-quiche)
  ESNI:             no      (--enable-esni)
  Protocols:        DICT FILE FTP GOPHER HTTP IMAP MQTT POP3 RTSP SMTP TELNET TFTP
  Features:         AsynchDNS IPv6 PSL UnixSockets 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-ssl, --with-gnutls, --with-wolfssl, --with-mbedtls, --with-nss, --with-schannel, --with-secure-transport, --with-mesalink, --with-amissl or --with-bearssl to address this.
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-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-dotdot.lo
  CC       libcurl_la-easy.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-url.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-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-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-doh.lo
  CC       libcurl_la-rand.lo
  CC       libcurl_la-rename.lo
  CC       libcurl_la-rtsp.lo
  CC       libcurl_la-security.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-urlapi.lo
  CC       libcurl_la-version.lo
  CC       libcurl_la-warnless.lo
  CC       libcurl_la-wildcard.lo
  CC       libcurl_la-dynbuf.lo
  CC       libcurl_la-x509asn1.lo
  CC       libcurl_la-version_win32.lo
  CC       libcurl_la-easyoptions.lo
  CC       libcurl_la-easygetopt.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-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-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       curl-slist_wc.o
  CC       curl-tool_bname.o
  CC       curl-tool_binmode.o
  CC       curl-tool_cb_dbg.o
  CC       curl-tool_cb_hdr.o
  CC       curl-tool_cb_prg.o
  CC       curl-tool_cb_see.o
  CC       curl-tool_cb_rea.o
  CC       curl-tool_cb_wrt.o
  CC       curl-tool_convert.o
  CC       curl-tool_dirhie.o
  CC       curl-tool_cfgable.o
  CC       curl-tool_doswin.o
  CC       curl-tool_easysrc.o
  CC       curl-tool_filetime.o
  CC       curl-tool_formparse.o
  CC       curl-tool_getparam.o
  CC       curl-tool_getpass.o
  CC       curl-tool_help.o
  CC       curl-tool_helpers.o
  CC       curl-tool_homedir.o
  HUGE     tool_hugehelp.c
  CC       curl-tool_libinfo.o
  CC       curl-tool_main.o
  CC       curl-tool_metalink.o
  CC       curl-tool_msgs.o
  CC       curl-tool_operate.o
  CC       curl-tool_operhlp.o
  CC       curl-tool_panykey.o
  CC       curl-tool_paramhlp.o
  CC       curl-tool_parsecfg.o
  CC       curl-tool_progress.o
  CC       curl-tool_strdup.o
  CC       curl-tool_setopt.o
  CC       curl-tool_sleep.o
  CC       curl-tool_urlglob.o
  CC       curl-tool_util.o
  CC       curl-tool_vms.o
  CC       curl-tool_writeout.o
  CC       curl-tool_writeout_json.o
  CC       curl-tool_xattr.o
  CC       ../lib/curl-strtoofft.o
  CC       ../lib/curl-nonblock.o
  CC       ../lib/curl-warnless.o
  CC       ../lib/curl-curl_ctype.o
  CC       ../lib/curl-curl_multibyte.o
  CC       ../lib/curl-version_win32.o
  CC       ../lib/curl-dynbuf.o
  CC       curl-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/Makefile.am +1 -1 docs/TheArtOfHttpScripting +0 -758 docs/TheArtOfHttpScripting.md +692 -0

docs/Makefile.am+1 -1

@@ -84,7 +84,7 @@ EXTRA_DIST = \
	SSLCERTS.md \
	THANKS \
	TODO \
-	TheArtOfHttpScripting \
+	TheArtOfHttpScripting.md \
	VERSIONS.md

	MAN2HTML= roffit $< >$@

docs/TheArtOfHttpScripting+0 -758

@@ -1,758 +0,0 @@
-	_ _ ____ _
-	___\| \| \| \| _ \\| \|
-	/ __\| \| \| \| \|_) \| \|
-	\| (__\| \|_\| \| _ <\| \|___
-	\___\|\___/\|_\| \_\_____\|
-
-
-	The Art Of Scripting HTTP Requests Using Curl
-
-	1. HTTP Scripting
-	1.1 Background
-	1.2 The HTTP Protocol
-	1.3 See the Protocol
-	1.4 See the Timing
-	1.5 See the Response
-	2. URL
-	2.1 Spec
-	2.2 Host
-	2.3 Port number
-	2.4 User name and password
-	2.5 Path part
-	3. Fetch a page
-	3.1 GET
-	3.2 HEAD
-	3.3 Multiple URLs in a single command line
-	3.4 Multiple HTTP methods in a single command line
-	4. HTML forms
-	4.1 Forms explained
-	4.2 GET
-	4.3 POST
-	4.4 File Upload POST
-	4.5 Hidden Fields
-	4.6 Figure Out What A POST Looks Like
-	5. HTTP upload
-	5.1 PUT
-	6. HTTP Authentication
-	6.1 Basic Authentication
-	6.2 Other Authentication
-	6.3 Proxy Authentication
-	6.4 Hiding credentials
-	7. More HTTP Headers
-	7.1 Referer
-	7.2 User Agent
-	8. Redirects
-	8.1 Location header
-	8.2 Other redirects
-	9. Cookies
-	9.1 Cookie Basics
-	9.2 Cookie options
-	10. HTTPS
-	10.1 HTTPS is HTTP secure
-	10.2 Certificates
-	11. Custom Request Elements
-	11.1 Modify method and headers
-	11.2 More on changed methods
-	12. Web Login
-	12.1 Some login tricks
-	13. Debug
-	13.1 Some debug tricks
-	14. References
-	14.1 Standards
-	14.2 Sites
-
-	==============================================================================
-
-	1. HTTP Scripting
-
-	1.1 Background
-
-	This document assumes that you're familiar with HTML and general networking.
-
-	The increasing amount of applications moving to the web has made "HTTP
-	Scripting" more frequently requested and wanted. To be able to automatically
-	extract information from the web, to fake users, to post or upload data to
-	web servers are all important tasks today.
-
-	Curl is a command line tool for doing all sorts of URL manipulations and
-	transfers, but this particular document will focus on how to use it when
-	doing HTTP requests for fun and profit. I'll assume that you know how to
-	invoke 'curl --help' or 'curl --manual' to get basic information about it.
-
-	Curl is not written to do everything for you. It makes the requests, it gets
-	the data, it sends data and it retrieves the information. You probably need
-	to glue everything together using some kind of script language or repeated
-	manual invokes.
-
-	1.2 The HTTP Protocol
-
-	HTTP is the protocol used to fetch data from web servers. It is a very 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.
-
-	HTTP is plain ASCII text lines being sent by the client to a server to
-	request a particular action, and then the server replies a few text lines
-	before the actual requested content is sent to the client.
-
-	The client, curl, sends a HTTP request. The request contains a method (like
-	GET, POST, HEAD etc), a number of request headers and sometimes a request
-	body. The HTTP server responds with a status line (indicating if things went
-	well), response headers and most often also a response body. The "body" part
-	is the plain data you requested, like the actual HTML or the image etc.
-
-	1.3 See the Protocol
-
-	Using curl's option --verbose (-v as a short option) will display what kind
-	of commands curl sends to the server, as well as a few other informational
-	texts.
-
-	--verbose is the single most useful option when it comes to debug or even
-	understand the curl<->server interaction.
-
-	Sometimes even --verbose is not enough. Then --trace and --trace-ascii offer
-	even more details as they show EVERYTHING curl sends and receives. Use it
-	like this:
-
-	curl --trace-ascii debugdump.txt http://www.example.com/
-
-	1.4 See the Timing
-
-	Many times you may wonder what exactly is taking all the time, or you just
-	want to know the amount of milliseconds between two points in a
-	transfer. For those, and other similar situations, the --trace-time option
-	is what you need. It'll prepend the time to each trace output line:
-
-	curl --trace-ascii d.txt --trace-time http://example.com/
-
-	1.5 See the Response
-
-	By default curl sends the response to stdout. You need to redirect it
-	somewhere to avoid that, most often that is done with -o or -O.
-
-	2. URL
-
-	2.1 Spec
-
-	The Uniform Resource Locator format is how you specify the address of a
-	particular resource on the Internet. You know these, you've seen URLs like
-	https://curl.haxx.se or https://yourbank.com a million times. RFC 3986 is the
-	canonical spec. And yeah, the formal name is not URL, it is URI.
-
-	2.2 Host
-
-	The host name is usually resolved using DNS or your /etc/hosts file to an IP
-	address and that's what curl will communicate with. Alternatively you specify
-	the IP address directly in the URL instead of a name.
-
-	For development and other trying out situations, you can point to a different
-	IP address for a host name than what would otherwise be used, by using curl's
-	--resolve option:
-
-	curl --resolve www.example.org:80:127.0.0.1 http://www.example.org/
-
-	2.3 Port number
-
-	Each protocol curl supports operates on a default port number, be it over TCP
-	or in some cases UDP. Normally you don't have to take that into
-	consideration, but at times you run test servers on other ports or
-	similar. Then you can specify the port number in the URL with a colon and a
-	number immediately following the host name. Like when doing HTTP to port
-	1234:
-
-	curl http://www.example.org:1234/
-
-	The port number you specify in the URL is the number that the server uses to
-	offer its services. Sometimes you may use a local proxy, and then you may
-	need to specify that proxy's port number separately for what curl needs to
-	connect to locally. Like when using a HTTP proxy on port 4321:
-
-	curl --proxy http://proxy.example.org:4321 http://remote.example.org/
-
-	2.4 User name and password
-
-	Some services are setup to require HTTP authentication and then you need to
-	provide name and password which is then transferred to the remote site in
-	various ways depending on the exact authentication protocol used.
-
-	You can opt to either insert the user and password in the URL or you can
-	provide them separately:
-
-	curl http://user:[email protected]/
-
-	or
-
-	curl -u user:password http://example.org/
-
-	You need to pay attention that this kind of HTTP authentication is not what
-	is usually done and requested by user-oriented websites these days. They
-	tend to use forms and cookies instead.
-
-	2.5 Path part
-
-	The path part is just sent off to the server to request that it sends back
-	the associated response. The path is what is to the right side of the slash
-	that follows the host name and possibly port number.
-
-	3. Fetch a page
-
-	3.1 GET
-
-	The simplest and most common request/operation made using HTTP is to GET a
-	URL. The URL could itself refer to a web page, an image or a file. The client
-	issues a GET request to the server and receives the document it asked for.
-	If you issue the command line
-
-	curl https://curl.haxx.se
-
-	you get a web page returned in your terminal window. The entire HTML document
-	that that URL holds.
-
-	All HTTP replies contain a set of response headers that are normally hidden,
-	use curl's --include (-i) option to display them as well as the rest of the
-	document.
-
-	3.2 HEAD
-
-	You can ask the remote server for ONLY the headers by using the --head (-I)
-	option which will make curl issue a HEAD request. In some special cases
-	servers deny the HEAD method while others still work, which is a particular
-	kind of annoyance.
-
-	The HEAD method is defined and made so that the server returns the headers
-	exactly the way it would do for a GET, but without a body. It means that you
-	may see a Content-Length: in the response headers, but there must not be an
-	actual body in the HEAD response.
-
-	3.3 Multiple URLs in a single command line
-
-	A single curl command line may involve one or many URLs. The most common case
-	is probably to just use one, but you can specify any amount of URLs. Yes
-	any. No limits. You'll then get requests repeated over and over for all the
-	given URLs.
-
-	Example, send two GETs:
-
-	curl http://url1.example.com http://url2.example.com
-
-	If you use --data to POST to the URL, using multiple URLs means that you send
-	that same POST to all the given URLs.
-
-	Example, send two POSTs:
-
-	curl --data name=curl http://url1.example.com http://url2.example.com
-
-
-	3.4 Multiple HTTP methods in a single command line
-
-	Sometimes you need to operate on several URLs in a single command line and do
-	different HTTP methods on each. For this, you'll enjoy the --next option. It
-	is basically a separator that separates a bunch of options from the next. All
-	the URLs before --next will get the same method and will get all the POST
-	data merged into one.
-
-	When curl reaches the --next on the command line, it'll sort of reset the
-	method and the POST data and allow a new set.
-
-	Perhaps this is best shown with a few examples. To send first a HEAD and then
-	a GET:
-
-	curl -I http://example.com --next http://example.com
-
-	To first send a POST and then a GET:
-
-	curl -d score=10 http://example.com/post.cgi --next http://example.com/results.html
-
-
-	4. HTML forms
-
-	4.1 Forms explained
-
-	Forms are the general way a website can present a HTML page with fields for
-	the user to enter data in, and then press some kind of 'OK' or 'Submit'
-	button to get that data sent to the server. The server then typically uses
-	the posted data to decide how to act. Like using the entered words to search
-	in a database, or to add the info in a bug tracking system, display the entered
-	address on a map or using the info as a login-prompt verifying that the user
-	is allowed to see what it is about to see.
-
-	Of course there has to be some kind of program on the server end to receive
-	the data you send. You cannot just invent something out of the air.
-
-	4.2 GET
-
-	A GET-form uses the method GET, as specified in HTML like:
-
-	<form method="GET" action="junk.cgi">
-	<input type=text name="birthyear">
-	<input type=submit name=press value="OK">
-	</form>
-
-	In your favorite browser, this form will appear with a text box to fill in
-	and a press-button labeled "OK". If you fill in '1905' and press the OK
-	button, your browser will then create a new URL to get for you. The URL will
-	get "junk.cgi?birthyear=1905&press=OK" appended to the path part of the
-	previous URL.
-
-	If the original form was seen on the page "www.hotmail.com/when/birth.html",
-	the second page you'll get will become
-	"www.hotmail.com/when/junk.cgi?birthyear=1905&press=OK".
-
-	Most search engines work this way.
-
-	To make curl do the GET form post for you, just enter the expected created
-	URL:
-
-	curl "http://www.hotmail.com/when/junk.cgi?birthyear=1905&press=OK"
-
-	4.3 POST
-
-	The GET method makes all input field names get displayed in the URL field of
-	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.
-
-	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:
-
-	<form method="POST" action="junk.cgi">
-	<input type=text name="birthyear">
-	<input type=submit name=press value=" OK ">
-	</form>
-
-	And to use curl to post this form with the same data filled in as before, we
-	could do it like:
-
-	curl --data "birthyear=1905&press=%20OK%20" \
-	http://www.example.com/when.cgi
-
-	This kind of POST will use the Content-Type
-	application/x-www-form-urlencoded and is the most widely used POST kind.
-
-	The data you send to the server MUST already be properly encoded, curl will
-	not do that for you. For example, if you want the data to contain a space,
-	you need to replace that space with %20 etc. Failing to comply with this
-	will most likely cause your data to be received wrongly and messed up.
-
-	Recent curl versions can in fact url-encode POST data for you, like this:
-
-	curl --data-urlencode "name=I am Daniel" http://www.example.com
-
-	If you repeat --data several times on the command line, curl will
-	concatenate all the given data pieces - and put a '&' symbol between each
-	data segment.
-
-	4.4 File Upload POST
-
-	Back in late 1995 they defined an additional way to post data over HTTP. It
-	is documented in the RFC 1867, why this method sometimes is referred to as
-	RFC1867-posting.
-
-	This method is mainly designed to better support file uploads. A form that
-	allows a user to upload a file could be written like this in HTML:
-
-	<form method="POST" enctype='multipart/form-data' action="upload.cgi">
-	<input type=file name=upload>
-	<input type=submit name=press value="OK">
-	</form>
-
-	This clearly shows that the Content-Type about to be sent is
-	multipart/form-data.
-
-	To post to a form like this with curl, you enter a command line like:
-
-	curl --form upload=@localfilename --form press=OK [URL]
-
-	4.5 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 similar example form with one visible field, one hidden field and one
-	submit button could look like:
-
-	<form method="POST" action="foobar.cgi">
-	<input type=text name="birthyear">
-	<input type=hidden name="person" value="daniel">
-	<input type=submit name="press" value="OK">
-	</form>
-
-	To POST this with curl, you won't have to think about if the fields are
-	hidden or not. To curl they're all the same:
-
-	curl --data "birthyear=1905&press=OK&person=daniel" [URL]
-
-	4.6 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.
-
-	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
-	(you could also change the action URL if you want to).
-
-	You will then clearly see the data get appended to the URL, separated with a
-	'?'-letter as GET forms are supposed to.
-
-	5. HTTP upload
-
-	5.1 PUT
-
-	Perhaps the best way to upload data to a HTTP server is to use PUT. Then
-	again, this of course requires that someone put a program or script on the
-	server end that knows how to receive a HTTP PUT stream.
-
-	Put a file to a HTTP server with curl:
-
-	curl --upload-file uploadfile http://www.example.com/receive.cgi
-
-	6. HTTP Authentication
-
-	6.1 Basic Authentication
-
-	HTTP Authentication is the ability to tell the server your username and
-	password so that it can verify that you're allowed to do the request you're
-	doing. The Basic authentication used in HTTP (which is the type curl uses by
-	default) is plain text based, which means it sends username and password
-	only slightly obfuscated, but still fully readable by anyone that sniffs on
-	the network between you and the remote server.
-
-	To tell curl to use a user and password for authentication:
-
-	curl --user name:password http://www.example.com
-
-	6.2 Other Authentication
-
-	The site might require a different authentication method (check the headers
-	returned by the server), and then --ntlm, --digest, --negotiate or even
-	--anyauth might be options that suit you.
-
-	6.3 Proxy Authentication
-
-	Sometimes your HTTP access is only available through the use of a HTTP
-	proxy. This seems to be especially common at various companies. A HTTP proxy
-	may require its own user and password to allow the client to get through to
-	the Internet. To specify those with curl, run something like:
-
-	curl --proxy-user proxyuser:proxypassword curl.haxx.se
-
-	If your proxy requires the authentication to be done using the NTLM method,
-	use --proxy-ntlm, if it requires Digest use --proxy-digest.
-
-	If you use any one of these user+password options but leave out the password
-	part, curl will prompt for the password interactively.
-
-	6.4 Hiding credentials
-
-	Do note that when a program is run, its parameters might be possible to see
-	when listing the running processes of the system. Thus, other users may be
-	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.
-
-	7. More HTTP Headers
-
-	7.1 Referer
-
-	A HTTP request may include a 'referer' field (yes it is misspelled), which
-	can be used to tell from which URL the client got to this particular
-	resource. Some programs/scripts check the referer field of requests to verify
-	that this wasn't arriving from an external site or an unknown page. While
-	this is a stupid way to check something so easily forged, many scripts still
-	do it. Using curl, you can put anything you want in the referer-field and
-	thus more easily be able to fool the server into serving your request.
-
-	Use curl to set the referer field with:
-
-	curl --referer http://www.example.come http://www.example.com
-
-	7.2 User Agent
-
-	Very 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
-	make them look the best possible for their particular browsers. They usually
-	also do different kinds of javascript, vbscript etc.
-
-	At times, you will see that getting a page with curl will not return the same
-	page that you see when getting the page with your browser. Then you know it
-	is time to set the User Agent field to fool the server into thinking you're
-	one of those browsers.
-
-	To make curl look like Internet Explorer 5 on a Windows 2000 box:
-
-	curl --user-agent "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" [URL]
-
-	Or why not look like you're using Netscape 4.73 on an old Linux box:
-
-	curl --user-agent "Mozilla/4.73 [en] (X11; U; Linux 2.2.15 i686)" [URL]
-
-	8. Redirects
-
-	8.1 Location header
-
-	When a resource is requested from a server, the reply from the server may
-	include a hint about where the browser should go next to find this page, or a
-	new page keeping newly generated output. The header that tells the browser
-	to redirect is Location:.
-
-	Curl does not follow Location: headers by default, but will simply display
-	such pages in the same manner it displays all HTTP replies. It does however
-	feature an option that will make it attempt to follow the Location: pointers.
-
-	To tell curl to follow a Location:
-
-	curl --location http://www.example.com
-
-	If you use curl to POST to a site that immediately redirects you to another
-	page, you can safely use --location (-L) and --data/--form together. Curl will
-	only use POST in the first request, and then revert to GET in the following
-	operations.
-
-	8.2 Other redirects
-
-	Browser typically support at least two other ways of redirects that curl
-	doesn't: first the html may contain a meta refresh tag that asks the browser
-	to load a specific URL after a set number of seconds, or it may use
-	javascript to do it.
-
-	9. Cookies
-
-	9.1 Cookie Basics
-
-	The way the web browsers do "client side state control" is by using
-	cookies. Cookies are just names with associated contents. The cookies are
-	sent to the client by the server. The server tells the client for what path
-	and host name it wants the cookie sent back, and it also sends an expiration
-	date and a few more properties.
-
-	When a client communicates with a server with a name and path as previously
-	specified in a received cookie, the client sends back the cookies and their
-	contents to the server, unless of course they are expired.
-
-	Many applications and servers use this method to connect a series of requests
-	into a single logical session. To be able to use curl in such occasions, we
-	must be able to record and send back cookies the way the web application
-	expects them. The same way browsers deal with them.
-
-	9.2 Cookie options
-
-	The simplest way to send a few cookies to the server when getting a page with
-	curl is to add them on the command line like:
-
-	curl --cookie "name=Daniel" http://www.example.com
-
-	Cookies are sent as common HTTP headers. This is practical as it allows curl
-	to record cookies simply by recording headers. Record cookies with curl by
-	using the --dump-header (-D) option like:
-
-	curl --dump-header headers_and_cookies http://www.example.com
-
-	(Take note that the --cookie-jar option described below is a better way to
-	store cookies.)
-
-	Curl has a full blown cookie parsing engine built-in that comes in use if you
-	want to reconnect to a server and use cookies that were stored from a
-	previous connection (or hand-crafted manually to fool the server into
-	believing you had a previous connection). To use previously stored cookies,
-	you run curl like:
-
-	curl --cookie stored_cookies_in_file http://www.example.com
-
-	Curl's "cookie engine" gets enabled when you use the --cookie option. If you
-	only want curl to understand received cookies, use --cookie with a file that
-	doesn't exist. Example, if you want to let curl understand cookies from a
-	page and follow a location (and thus possibly send back cookies it received),
-	you can invoke it like:
-
-	curl --cookie nada --location http://www.example.com
-
-	Curl has the ability to read and write cookie files that use the same file
-	format that Netscape and Mozilla once used. It is a convenient way to share
-	cookies between scripts or invokes. The --cookie (-b) switch automatically
-	detects if a given file is such a cookie file and parses it, and by using the
-	--cookie-jar (-c) option you'll make curl write a new cookie file at the end
-	of an operation:
-
-	curl --cookie cookies.txt --cookie-jar newcookies.txt \
-	http://www.example.com
-
-	10. HTTPS
-
-	10.1 HTTPS is HTTP secure
-
-	There are a few ways to do secure HTTP transfers. By far the most common
-	protocol for doing this is what is generally known as HTTPS, HTTP over
-	SSL. SSL encrypts all the data that is sent and received over the network and
-	thus makes it harder for attackers to spy on sensitive information.
-
-	SSL (or TLS as the latest version of the standard is called) offers a
-	truckload of advanced features to allow all those encryptions and key
-	infrastructure mechanisms encrypted HTTP requires.
-
-	Curl supports encrypted fetches when built to use a TLS library and it can be
-	built to use one out of a fairly large set of libraries - "curl -V" will show
-	which one your curl was built to use (if any!). To get a page from a HTTPS
-	server, simply run curl like:
-
-	curl https://secure.example.com
-
-	10.2 Certificates
-
-	In the HTTPS world, you use certificates to validate that you are the one
-	you claim to be, as an addition to normal passwords. Curl supports client-
-	side certificates. All certificates are locked with a pass phrase, which you
-	need to enter before the certificate can be used by curl. The pass phrase
-	can be specified on the command line or if not, entered interactively when
-	curl queries for it. Use a certificate with curl on a HTTPS server like:
-
-	curl --cert mycert.pem https://secure.example.com
-
-	curl also tries to verify that the server is who it claims to be, by
-	verifying the server's certificate against a locally stored CA cert
-	bundle. Failing the verification will cause curl to deny the connection. You
-	must then use --insecure (-k) in case you want to tell curl to ignore that
-	the server can't be verified.
-
-	More about server certificate verification and ca cert bundles can be read
-	in the SSLCERTS document, available online here:
-
-	https://curl.haxx.se/docs/sslcerts.html
-
-	At times you may end up with your own CA cert store and then you can tell
-	curl to use that to verify the server's certificate:
-
-	curl --cacert ca-bundle.pem https://example.com/
-
-
-	11. Custom Request Elements
-
-	11.1 Modify method and headers
-
-	Doing fancy stuff, you may need to add or change elements of a single curl
-	request.
-
-	For example, you can change the POST request to a PROPFIND and send the data
-	as "Content-Type: text/xml" (instead of the default Content-Type) like this:
-
-	curl --data "<xml>" --header "Content-Type: text/xml" \
-	--request PROPFIND url.com
-
-	You can delete a default header by providing one without content. Like you
-	can ruin the request by chopping off the Host: header:
-
-	curl --header "Host:" http://www.example.com
-
-	You can add headers the same way. Your server may want a "Destination:"
-	header, and you can add it:
-
-	curl --header "Destination: http://nowhere" http://example.com
-
-	11.2 More on changed methods
-
-	It should be noted that curl selects which methods to use on its own
-	depending on what action to ask for. -d will do POST, -I will do HEAD and so
-	on. If you use the --request / -X option you can change the method keyword
-	curl selects, but you will not modify curl's behavior. This means that if you
-	for example use -d "data" to do a POST, you can modify the method to a
-	PROPFIND with -X and curl will still think it sends a POST. You can change
-	the normal GET to a POST method by simply adding -X POST in a command line
-	like:
-
-	curl -X POST http://example.org/
-
-	... but curl will still think and act as if it sent a GET so it won't send any
-	request body etc.
-
-
-	12. Web Login
-
-	12.1 Some login tricks
-
-	While not strictly just HTTP related, it still causes a lot of people problems
-	so here's the executive run-down of how the vast majority of all login forms
-	work and how to login to them using curl.
-
-	It can also be noted that to do this properly in an automated fashion, you
-	will most certainly need to script things and do multiple curl invokes etc.
-
-	First, servers mostly use cookies to track the logged-in status of the
-	client, so you will need to capture the cookies you receive in the
-	responses. Then, many sites also set a special cookie on the login page (to
-	make sure you got there through their login page) so you should make a habit
-	of first getting the login-form page to capture the cookies set there.
-
-	Some web-based login systems feature various amounts of javascript, and
-	sometimes they use such code to set or modify cookie contents. Possibly they
-	do that to prevent programmed logins, like this manual describes how to...
-	Anyway, if reading the code isn't enough to let you repeat the behavior
-	manually, capturing the HTTP requests done by your browsers and analyzing the
-	sent cookies is usually a working method to work out how to shortcut the
-	javascript need.
-
-	In the actual <form> tag for the login, lots of sites fill-in random/session
-	or otherwise secretly generated hidden tags and you may need to first capture
-	the HTML code for the login form and extract all the hidden fields to be able
-	to do a proper login POST. Remember that the contents need to be URL encoded
-	when sent in a normal POST.
-
-	13. Debug
-
-	13.1 Some debug tricks
-
-	Many times when you run curl on a site, you'll notice that the site doesn't
-	seem to respond the same way to your curl requests as it does to your
-	browser's.
-
-	Then you need to start making your curl requests more similar to your
-	browser's requests:
-
-	* Use the --trace-ascii option to store fully detailed logs of the requests
-	for easier analyzing and better understanding
-
-	* Make sure you check for and use cookies when needed (both reading with
-	--cookie and writing with --cookie-jar)
-
-	* Set user-agent to one like a recent popular browser does
-
-	* Set referer like it is set by the browser
-
-	* If you use POST, make sure you send all the fields and in the same order as
-	the browser does it.
-
-	A very good helper to make sure you do this right, is the LiveHTTPHeader tool
-	that lets you view all headers you send and receive with Mozilla/Firefox
-	(even when using HTTPS). Chrome features similar functionality out of the box
-	among the developer's tools.
-
-	A more raw approach is to capture the HTTP traffic on the network with tools
-	such as ethereal or tcpdump and check what headers that were sent and
-	received by the browser. (HTTPS makes this technique inefficient.)
-
-	14. References
-
-	14.1 Standards
-
-	RFC 7230 is a must to read if you want in-depth understanding of the HTTP
-	protocol
-
-	RFC 3986 explains the URL syntax
-
-	RFC 1867 defines the HTTP post upload format
-
-	RFC 6525 defines how HTTP cookies work
-
-	14.2 Sites
-
-	https://curl.haxx.se is the home of the curl project

docs/TheArtOfHttpScripting.md+692 -0

@@ -0,0 +1,692 @@
+	# The Art Of Scripting HTTP Requests Using Curl
+
+	## Background
+
+	This document assumes that you're familiar with HTML and general networking.
+
+	The increasing amount of applications moving to the web has made "HTTP
+	Scripting" more frequently requested and wanted. To be able to automatically
+	extract information from the web, to fake users, to post or upload data to
+	web servers are all important tasks today.
+
+	Curl is a command line tool for doing all sorts of URL manipulations and
+	transfers, but this particular document will focus on how to use it when
+	doing HTTP requests for fun and profit. I willl assume that you know how to
+	invoke `curl --help` or `curl --manual` to get basic information about it.
+
+	Curl is not written to do everything for you. It makes the requests, it gets
+	the data, it sends data and it retrieves the information. You probably need
+	to glue everything together using some kind of script language or repeated
+	manual invokes.
+
+	## The HTTP Protocol
+
+	HTTP is the protocol used to fetch data from web servers. It is a very 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.
+
+	HTTP is plain ASCII text lines being sent by the client to a server to
+	request a particular action, and then the server replies a few text lines
+	before the actual requested content is sent to the client.
+
+	The client, curl, sends a HTTP request. The request contains a method (like
+	GET, POST, HEAD etc), a number of request headers and sometimes a request
+	body. The HTTP server responds with a status line (indicating if things went
+	well), response headers and most often also a response body. The "body" part
+	is the plain data you requested, like the actual HTML or the image etc.
+
+	## See the Protocol
+
+	Using curl's option [`--verbose`](https://curl.haxx.se/docs/manpage.html#-v)
+	(`-v` as a short option) will display what kind of commands curl sends to the
+	server, as well as a few other informational texts.
+
+	`--verbose` is the single most useful option when it comes to debug or even
+	understand the curl<->server interaction.
+
+	Sometimes even `--verbose` is not enough. Then
+	[`--trace`](https://curl.haxx.se/docs/manpage.html#-trace) and
+	[`--trace-ascii`]((https://curl.haxx.se/docs/manpage.html#--trace-ascii)
+	offer even more details as they show everything curl sends and
+	receives. Use it like this:
+
+	curl --trace-ascii debugdump.txt http://www.example.com/
+
+	## See the Timing
+
+	Many times you may wonder what exactly is taking all the time, or you just
+	want to know the amount of milliseconds between two points in a transfer. For
+	those, and other similar situations, the
+	[`--trace-time`]((https://curl.haxx.se/docs/manpage.html#--trace-time) option
+	is what you need. It'll prepend the time to each trace output line:
+
+	curl --trace-ascii d.txt --trace-time http://example.com/
+
+	## See the Response
+
+	By default curl sends the response to stdout. You need to redirect it
+	somewhere to avoid that, most often that is done with ` -o` or `-O`.
+
+	# URL
+
+	## Spec
+
+	The Uniform Resource Locator format is how you specify the address of a
+	particular resource on the Internet. You know these, you've seen URLs like
+	https://curl.haxx.se or https://yourbank.com a million times. RFC 3986 is the
+	canonical spec. And yeah, the formal name is not URL, it is URI.
+
+	## Host
+
+	The host name is usually resolved using DNS or your /etc/hosts file to an IP
+	address and that's what curl will communicate with. Alternatively you specify
+	the IP address directly in the URL instead of a name.
+
+	For development and other trying out situations, you can point to a different
+	IP address for a host name than what would otherwise be used, by using curl's
+	[`--resolve`](https://curl.haxx.se/docs/manpage.html#--resolve) option:
+
+	curl --resolve www.example.org:80:127.0.0.1 http://www.example.org/
+
+	## Port number
+
+	Each protocol curl supports operates on a default port number, be it over TCP
+	or in some cases UDP. Normally you don't have to take that into
+	consideration, but at times you run test servers on other ports or
+	similar. Then you can specify the port number in the URL with a colon and a
+	number immediately following the host name. Like when doing HTTP to port
+	1234:
+
+	curl http://www.example.org:1234/
+
+	The port number you specify in the URL is the number that the server uses to
+	offer its services. Sometimes you may use a local proxy, and then you may
+	need to specify that proxy's port number separately for what curl needs to
+	connect to locally. Like when using a HTTP proxy on port 4321:
+
+	curl --proxy http://proxy.example.org:4321 http://remote.example.org/
+
+	## User name and password
+
+	Some services are setup to require HTTP authentication and then you need to
+	provide name and password which is then transferred to the remote site in
+	various ways depending on the exact authentication protocol used.
+
+	You can opt to either insert the user and password in the URL or you can
+	provide them separately:
+
+	curl http://user:[email protected]/
+
+	or
+
+	curl -u user:password http://example.org/
+
+	You need to pay attention that this kind of HTTP authentication is not what
+	is usually done and requested by user-oriented websites these days. They tend
+	to use forms and cookies instead.
+
+	## Path part
+
+	The path part is just sent off to the server to request that it sends back
+	the associated response. The path is what is to the right side of the slash
+	that follows the host name and possibly port number.
+
+	# Fetch a page
+
+	## GET
+
+	The simplest and most common request/operation made using HTTP is to GET a
+	URL. The URL could itself refer to a web page, an image or a file. The client
+	issues a GET request to the server and receives the document it asked for.
+	If you issue the command line
+
+	curl https://curl.haxx.se
+
+	you get a web page returned in your terminal window. The entire HTML document
+	that that URL holds.
+
+	All HTTP replies contain a set of response headers that are normally hidden,
+	use curl's [`--include`](https://curl.haxx.se/docs/manpage.html#-i) (`-i`)
+	option to display them as well as the rest of the document.
+
+	## HEAD
+
+	You can ask the remote server for ONLY the headers by using the
+	[`--head`](https://curl.haxx.se/docs/manpage.html#-I) (`-I`) option which
+	will make curl issue a HEAD request. In some special cases servers deny the
+	HEAD method while others still work, which is a particular kind of annoyance.
+
+	The HEAD method is defined and made so that the server returns the headers
+	exactly the way it would do for a GET, but without a body. It means that you
+	may see a `Content-Length:` in the response headers, but there must not be an
+	actual body in the HEAD response.
+
+	## Multiple URLs in a single command line
+
+	A single curl command line may involve one or many URLs. The most common case
+	is probably to just use one, but you can specify any amount of URLs. Yes
+	any. No limits. You'll then get requests repeated over and over for all the
+	given URLs.
+
+	Example, send two GETs:
+
+	curl http://url1.example.com http://url2.example.com
+
+	If you use [`--data`](https://curl.haxx.se/docs/manpage.html#-d) to POST to
+	the URL, using multiple URLs means that you send that same POST to all the
+	given URLs.
+
+	Example, send two POSTs:
+
+	curl --data name=curl http://url1.example.com http://url2.example.com
+
+
+	## Multiple HTTP methods in a single command line
+
+	Sometimes you need to operate on several URLs in a single command line and do
+	different HTTP methods on each. For this, you'll enjoy the
+	[`--next`](https://curl.haxx.se/docs/manpage.html#-:) option. It is basically
+	a separator that separates a bunch of options from the next. All the URLs
+	before `--next` will get the same method and will get all the POST data
+	merged into one.
+
+	When curl reaches the `--next` on the command line, it'll sort of reset the
+	method and the POST data and allow a new set.
+
+	Perhaps this is best shown with a few examples. To send first a HEAD and then
+	a GET:
+
+	curl -I http://example.com --next http://example.com
+
+	To first send a POST and then a GET:
+
+	curl -d score=10 http://example.com/post.cgi --next http://example.com/results.html
+
+	# HTML forms
+
+	## Forms explained
+
+	Forms are the general way a website can present a HTML page with fields for
+	the user to enter data in, and then press some kind of 'OK' or 'Submit'
+	button to get that data sent to the server. The server then typically uses
+	the posted data to decide how to act. Like using the entered words to search
+	in a database, or to add the info in a bug tracking system, display the
+	entered address on a map or using the info as a login-prompt verifying that
+	the user is allowed to see what it is about to see.
+
+	Of course there has to be some kind of program on the server end to receive
+	the data you send. You cannot just invent something out of the air.
+
+	## GET
+
+	A GET-form uses the method GET, as specified in HTML like:
+
+	<form method="GET" action="junk.cgi">
+	<input type=text name="birthyear">
+	<input type=submit name=press value="OK">
+	</form>
+
+	In your favorite browser, this form will appear with a text box to fill in
+	and a press-button labeled "OK". If you fill in '1905' and press the OK
+	button, your browser will then create a new URL to get for you. The URL will
+	get `junk.cgi?birthyear=1905&press=OK` appended to the path part of the
+	previous URL.
+
+	If the original form was seen on the page `www.example.com/when/birth.html`,
+	the second page you'll get will become
+	`www.example.com/when/junk.cgi?birthyear=1905&press=OK`.
+
+	Most search engines work this way.
+
+	To make curl do the GET form post for you, just enter the expected created
+	URL:
+
+	curl "http://www.example.com/when/junk.cgi?birthyear=1905&press=OK"
+
+	## POST
+
+	The GET method makes all input field names get displayed in the URL field of
+	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.
+
+	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:
+
+	<form method="POST" action="junk.cgi">
+	<input type=text name="birthyear">
+	<input type=submit name=press value=" OK ">
+	</form>
+
+	And to use curl to post this form with the same data filled in as before, we
+	could do it like:
+
+	curl --data "birthyear=1905&press=%20OK%20" http://www.example.com/when.cgi
+
+	This kind of POST will use the Content-Type
+	`application/x-www-form-urlencoded' and is the most widely used POST kind.
+
+	The data you send to the server MUST already be properly encoded, curl will
+	not do that for you. For example, if you want the data to contain a space,
+	you need to replace that space with %20 etc. Failing to comply with this will
+	most likely cause your data to be received wrongly and messed up.
+
+	Recent curl versions can in fact url-encode POST data for you, like this:
+
+	curl --data-urlencode "name=I am Daniel" http://www.example.com
+
+	If you repeat `--data` several times on the command line, curl will
+	concatenate all the given data pieces - and put a `&` symbol between each
+	data segment.
+
+	## File Upload POST
+
+	Back in late 1995 they defined an additional way to post data over HTTP. It
+	is documented in the RFC 1867, why this method sometimes is referred to as
+	RFC1867-posting.
+
+	This method is mainly designed to better support file uploads. A form that
+	allows a user to upload a file could be written like this in HTML:
+
+	<form method="POST" enctype='multipart/form-data' action="upload.cgi">
+	<input type=file name=upload>
+	<input type=submit name=press value="OK">
+	</form>
+
+	This clearly shows that the Content-Type about to be sent is
+	`multipart/form-data`.
+
+	To post to a form like this with curl, you enter a command line like:
+
+	curl --form upload=@localfilename --form press=OK [URL]
+
+	## 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 similar example form with one visible field, one hidden field and one
+	submit button could look like:
+
+	<form method="POST" action="foobar.cgi">
+	<input type=text name="birthyear">
+	<input type=hidden name="person" value="daniel">
+	<input type=submit name="press" value="OK">
+	</form>
+
+	To POST this with curl, you won't have to think about if the fields are
+	hidden or not. To curl they're all the same:
+
+	curl --data "birthyear=1905&press=OK&person=daniel" [URL]
+
+	## 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.
+
+	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
+	(you could also change the action URL if you want to).
+
+	You will then clearly see the data get appended to the URL, separated with a
+	`?`-letter as GET forms are supposed to.
+
+	# HTTP upload
+
+	## PUT
+
+	Perhaps the best way to upload data to a HTTP server is to use PUT. Then
+	again, this of course requires that someone put a program or script on the
+	server end that knows how to receive a HTTP PUT stream.
+
+	Put a file to a HTTP server with curl:
+
+	curl --upload-file uploadfile http://www.example.com/receive.cgi
+
+	# HTTP Authentication
+
+	## Basic Authentication
+
+	HTTP Authentication is the ability to tell the server your username and
+	password so that it can verify that you're allowed to do the request you're
+	doing. The Basic authentication used in HTTP (which is the type curl uses by
+	default) is plain text based, which means it sends username and password
+	only slightly obfuscated, but still fully readable by anyone that sniffs on
+	the network between you and the remote server.
+
+	To tell curl to use a user and password for authentication:
+
+	curl --user name:password http://www.example.com
+
+	## Other Authentication
+
+	The site might require a different authentication method (check the headers
+	returned by the server), and then
+	[`--ntlm`](https://curl.haxx.se/docs/manpage.html#--ntlm),
+	[`--digest`](https://curl.haxx.se/docs/manpage.html#--digest),
+	[`--negotiate`](https://curl.haxx.se/docs/manpage.html#--negotiate) or even
+	[`--anyauth`](https://curl.haxx.se/docs/manpage.html#--anyauth) might be
+	options that suit you.
+
+	## Proxy Authentication
+
+	Sometimes your HTTP access is only available through the use of a HTTP
+	proxy. This seems to be especially common at various companies. A HTTP proxy
+	may require its own user and password to allow the client to get through to
+	the Internet. To specify those with curl, run something like:
+
+	curl --proxy-user proxyuser:proxypassword curl.haxx.se
+
+	If your proxy requires the authentication to be done using the NTLM method,
+	use [`--proxy-ntlm`](https://curl.haxx.se/docs/manpage.html#--proxy-ntlm), if
+	it requires Digest use
+	[`--proxy-digest`](https://curl.haxx.se/docs/manpage.html#--proxy-digest).
+
+	If you use any one of these user+password options but leave out the password
+	part, curl will prompt for the password interactively.
+
+	## Hiding credentials
+
+	Do note that when a program is run, its parameters might be possible to see
+	when listing the running processes of the system. Thus, other users may be
+	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.
+
+	# More HTTP Headers
+
+	## Referer
+
+	A HTTP request may include a 'referer' field (yes it is misspelled), which
+	can be used to tell from which URL the client got to this particular
+	resource. Some programs/scripts check the referer field of requests to verify
+	that this wasn't arriving from an external site or an unknown page. While
+	this is a stupid way to check something so easily forged, many scripts still
+	do it. Using curl, you can put anything you want in the referer-field and
+	thus more easily be able to fool the server into serving your request.
+
+	Use curl to set the referer field with:
+
+	curl --referer http://www.example.come http://www.example.com
+
+	## User Agent
+
+	Very 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
+	make them look the best possible for their particular browsers. They usually
+	also do different kinds of javascript, vbscript etc.
+
+	At times, you will see that getting a page with curl will not return the same
+	page that you see when getting the page with your browser. Then you know it
+	is time to set the User Agent field to fool the server into thinking you're
+	one of those browsers.
+
+	To make curl look like Internet Explorer 5 on a Windows 2000 box:
+
+	curl --user-agent "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)" [URL]
+
+	Or why not look like you're using Netscape 4.73 on an old Linux box:
+
+	curl --user-agent "Mozilla/4.73 [en] (X11; U; Linux 2.2.15 i686)" [URL]
+
+	## Redirects
+
+	## Location header
+
+	When a resource is requested from a server, the reply from the server may
+	include a hint about where the browser should go next to find this page, or a
+	new page keeping newly generated output. The header that tells the browser to
+	redirect is `Location:`.
+
+	Curl does not follow `Location:` headers by default, but will simply display
+	such pages in the same manner it displays all HTTP replies. It does however
+	feature an option that will make it attempt to follow the `Location:`
+	pointers.
+
+	To tell curl to follow a Location:
+
+	curl --location http://www.example.com
+
+	If you use curl to POST to a site that immediately redirects you to another
+	page, you can safely use
+	[`--location`](https://curl.haxx.se/docs/manpage.html#-L) (`-L`) and
+	`--data`/`--form` together. curl will only use POST in the first request, and
+	then revert to GET in the following operations.
+
+	## Other redirects
+
+	Browser typically support at least two other ways of redirects that curl
+	doesn't: first the html may contain a meta refresh tag that asks the browser
+	to load a specific URL after a set number of seconds, or it may use
+	javascript to do it.
+
+	# Cookies
+
+	## Cookie Basics
+
+	The way the web browsers do "client side state control" is by using
+	cookies. Cookies are just names with associated contents. The cookies are
+	sent to the client by the server. The server tells the client for what path
+	and host name it wants the cookie sent back, and it also sends an expiration
+	date and a few more properties.
+
+	When a client communicates with a server with a name and path as previously
+	specified in a received cookie, the client sends back the cookies and their
+	contents to the server, unless of course they are expired.
+
+	Many applications and servers use this method to connect a series of requests
+	into a single logical session. To be able to use curl in such occasions, we
+	must be able to record and send back cookies the way the web application
+	expects them. The same way browsers deal with them.
+
+	## Cookie options
+
+	The simplest way to send a few cookies to the server when getting a page with
+	curl is to add them on the command line like:
+
+	curl --cookie "name=Daniel" http://www.example.com
+
+	Cookies are sent as common HTTP headers. This is practical as it allows curl
+	to record cookies simply by recording headers. Record cookies with curl by
+	using the [`--dump-header`](https://curl.haxx.se/docs/manpage.html#-D) (`-D`)
+	option like:
+
+	curl --dump-header headers_and_cookies http://www.example.com
+
+	(Take note that the
+	[`--cookie-jar`](https://curl.haxx.se/docs/manpage.html#-c) option described
+	below is a better way to store cookies.)
+
+	Curl has a full blown cookie parsing engine built-in that comes in use if you
+	want to reconnect to a server and use cookies that were stored from a
+	previous connection (or hand-crafted manually to fool the server into
+	believing you had a previous connection). To use previously stored cookies,
+	you run curl like:
+
+	curl --cookie stored_cookies_in_file http://www.example.com
+
+	Curl's "cookie engine" gets enabled when you use the
+	[`--cookie`](https://curl.haxx.se/docs/manpage.html#-b) option. If you only
+	want curl to understand received cookies, use `--cookie` with a file that
+	doesn't exist. Example, if you want to let curl understand cookies from a
+	page and follow a location (and thus possibly send back cookies it received),
+	you can invoke it like:
+
+	curl --cookie nada --location http://www.example.com
+
+	Curl has the ability to read and write cookie files that use the same file
+	format that Netscape and Mozilla once used. It is a convenient way to share
+	cookies between scripts or invokes. The `--cookie` (`-b`) switch
+	automatically detects if a given file is such a cookie file and parses it,
+	and by using the `--cookie-jar` (`-c`) option you'll make curl write a new
+	cookie file at the end of an operation:
+
+	curl --cookie cookies.txt --cookie-jar newcookies.txt \
+	http://www.example.com
+
+	# HTTPS
+
+	## HTTPS is HTTP secure
+
+	There are a few ways to do secure HTTP transfers. By far the most common
+	protocol for doing this is what is generally known as HTTPS, HTTP over
+	SSL. SSL encrypts all the data that is sent and received over the network and
+	thus makes it harder for attackers to spy on sensitive information.
+
+	SSL (or TLS as the latest version of the standard is called) offers a
+	truckload of advanced features to allow all those encryptions and key
+	infrastructure mechanisms encrypted HTTP requires.
+
+	Curl supports encrypted fetches when built to use a TLS library and it can be
+	built to use one out of a fairly large set of libraries - `curl -V` will show
+	which one your curl was built to use (if any!). To get a page from a HTTPS
+	server, simply run curl like:
+
+	curl https://secure.example.com
+
+	## Certificates
+
+	In the HTTPS world, you use certificates to validate that you are the one
+	you claim to be, as an addition to normal passwords. Curl supports client-
+	side certificates. All certificates are locked with a pass phrase, which you
+	need to enter before the certificate can be used by curl. The pass phrase
+	can be specified on the command line or if not, entered interactively when
+	curl queries for it. Use a certificate with curl on a HTTPS server like:
+
+	curl --cert mycert.pem https://secure.example.com
+
+	curl also tries to verify that the server is who it claims to be, by
+	verifying the server's certificate against a locally stored CA cert
+	bundle. Failing the verification will cause curl to deny the connection. You
+	must then use [`--insecure`](https://curl.haxx.se/docs/manpage.html#-k)
+	(`-k`) in case you want to tell curl to ignore that the server can't be
+	verified.
+
+	More about server certificate verification and ca cert bundles can be read in
+	the [SSLCERTS document](https://curl.haxx.se/docs/sslcerts.html).
+
+	At times you may end up with your own CA cert store and then you can tell
+	curl to use that to verify the server's certificate:
+
+	curl --cacert ca-bundle.pem https://example.com/
+
+	# Custom Request Elements
+
+	## Modify method and headers
+
+	Doing fancy stuff, you may need to add or change elements of a single curl
+	request.
+
+	For example, you can change the POST request to a PROPFIND and send the data
+	as `Content-Type: text/xml` (instead of the default Content-Type) like this:
+
+	curl --data "<xml>" --header "Content-Type: text/xml" \
+	--request PROPFIND example.com
+
+	You can delete a default header by providing one without content. Like you
+	can ruin the request by chopping off the Host: header:
+
+	curl --header "Host:" http://www.example.com
+
+	You can add headers the same way. Your server may want a `Destination:`
+	header, and you can add it:
+
+	curl --header "Destination: http://nowhere" http://example.com
+
+	## More on changed methods
+
+	It should be noted that curl selects which methods to use on its own
+	depending on what action to ask for. `-d` will do POST, `-I` will do HEAD and
+	so on. If you use the
+	[`--request`](https://curl.haxx.se/docs/manpage.html#-X) / `-X` option you
+	can change the method keyword curl selects, but you will not modify curl's
+	behavior. This means that if you for example use -d "data" to do a POST, you
+	can modify the method to a `PROPFIND` with `-X` and curl will still think it
+	sends a POST . You can change the normal GET to a POST method by simply
+	adding `-X POST` in a command line like:
+
+	curl -X POST http://example.org/
+
+	... but curl will still think and act as if it sent a GET so it won't send
+	any request body etc.
+
+	# Web Login
+
+	## Some login tricks
+
+	While not strictly just HTTP related, it still causes a lot of people
+	problems so here's the executive run-down of how the vast majority of all
+	login forms work and how to login to them using curl.
+
+	It can also be noted that to do this properly in an automated fashion, you
+	will most certainly need to script things and do multiple curl invokes etc.
+
+	First, servers mostly use cookies to track the logged-in status of the
+	client, so you will need to capture the cookies you receive in the
+	responses. Then, many sites also set a special cookie on the login page (to
+	make sure you got there through their login page) so you should make a habit
+	of first getting the login-form page to capture the cookies set there.
+
+	Some web-based login systems feature various amounts of javascript, and
+	sometimes they use such code to set or modify cookie contents. Possibly they
+	do that to prevent programmed logins, like this manual describes how to...
+	Anyway, if reading the code isn't enough to let you repeat the behavior
+	manually, capturing the HTTP requests done by your browsers and analyzing the
+	sent cookies is usually a working method to work out how to shortcut the
+	javascript need.
+
+	In the actual `<form>` tag for the login, lots of sites fill-in
+	random/session or otherwise secretly generated hidden tags and you may need
+	to first capture the HTML code for the login form and extract all the hidden
+	fields to be able to do a proper login POST. Remember that the contents need
+	to be URL encoded when sent in a normal POST.
+
+	# Debug
+
+	## Some debug tricks
+
+	Many times when you run curl on a site, you'll notice that the site doesn't
+	seem to respond the same way to your curl requests as it does to your
+	browser's.
+
+	Then you need to start making your curl requests more similar to your
+	browser's requests:
+
+	- Use the `--trace-ascii` option to store fully detailed logs of the requests
+	for easier analyzing and better understanding
+
+	- Make sure you check for and use cookies when needed (both reading with
+	`--cookie` and writing with `--cookie-jar`)
+
+	- Set user-agent (with [`-A`](https://curl.haxx.se/docs/manpage.html#-A)) to
+	one like a recent popular browser does
+
+	- Set referer (with [`-E`](https://curl.haxx.se/docs/manpage.html#-E)) like
+	it is set by the browser
+
+	- If you use POST, make sure you send all the fields and in the same order as
+	the browser does it.
+
+	## 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 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
+	received by the browser. (HTTPS forces you to use `SSLKEYLOGFILE` to do
+	that.)