From: Cary Lewis <cary.lewis@gmail.com>
To: cygwin@cygwin.com
Subject: curl not sending keep-alive packets
Date: Sat, 6 Jun 2020 08:56:58 -0400 [thread overview]
Message-ID: <CAEF1h+XtJZ2q=q5BPDwWcCeZg00ZK49y2i8d55JpZpT2hDEWXw@mail.gmail.com> (raw)
I downloaded and compiled curl on cygwin, version 3.1.5-1 using:
./configure --disable-shared --enable-debug --prefix=/usr
The build completed correctly.
When I attempt to use curl to access an https:// REST endpoint that takes
up to 5 minutes to respond with the:
--keepalive-time 5
command line option, and I watch the TCP traffic via wireshark, I do not
see any TCP Keep-Alive packets. Without the keep-alive packets the request
fails.
curl/libcurl version
curl 7.71.0-DEV (x86_64-pc-cygwin) libcurl/7.71.0-DEV OpenSSL/1.1.1f
zlib/1.2.11
Release-Date: [unreleased]
operating system
CYGWIN_NT-10.0 IT008 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
Running the win32 version of curl does work as expected, and I see the
Keep-Alive packets being sent every 5 seconds, and the REST call does
complete correctly.
The official curl build does not work any better, that's why I tried to
download and rebuild the code.
Does anyone know why the --keepalive-time option is not working with cygwin?
reply other threads:[~2020-06-06 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEF1h+XtJZ2q=q5BPDwWcCeZg00ZK49y2i8d55JpZpT2hDEWXw@mail.gmail.com' \
--to=cary.lewis@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).