From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Something makes curl hang for 5 minutes after connection refused
Date: Fri, 30 Nov 2018 19:49:00 -0000 [thread overview]
Message-ID: <CAD8GWssBAH_KKXCC7jxTgCjS02KjXVb7LgkNvyriXJeE7cPSOg@mail.gmail.com> (raw)
In-Reply-To: <8a710131-214c-badd-04a8-fc0899cf5511@gmail.com>
On 11/30/18, Basin Ilya wrote:
> Hi.
>
> Recently I noticed that `curl` does not fail immediately after connection
> refused, but waits for 5 minutes.
>
> This only happens on my machine and only with the `Cygwin` version of
> `curl`. The mingw version is unaffected.
> I tried downgrading curl, but it didn't help. I thought there's a rogue
> setting in `/etc` or in home or maybe some environment variable, but I
> couldn't find it.
>
> basin@BASIN /cygdrive/c/Users/basin
> $ >/dev/null /usr/bin/curl -v http://127.0.0.1:2/
> * STATE: INIT => CONNECT handle 0x80048658; line 1404 (connection
> #-5000)
> * Added connection 0. The cache now contains 1 members
> * Trying 127.0.0.1...
> * TCP_NODELAY set
> * STATE: CONNECT => WAITCONNECT handle 0x80048658; line 1456 (connection
> #0)
<.. snip ..>
> curl: (28) Connection timed out after 300145 milliseconds
>
> basin@BASIN /cygdrive/c/Users/basin
> $ /usr/bin/curl --version
> curl 7.59.0 (i686-pc-cygwin) libcurl/7.59.0 OpenSSL/1.0.2p zlib/1.2.11
> libidn2/2.0.4 libpsl/0.18.0 (+libidn2/2.0.2) libssh2/1.7.0 nghttp2/1.31.0
> Can someone try to reproduce it?
I get the same behavior:
$ /usr/bin/curl -v http://127.0.0.1:2/
* STATE: INIT => CONNECT handle 0x600057ad0; line 1404 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* Trying 127.0.0.1...
* TCP_NODELAY set
* STATE: CONNECT => WAITCONNECT handle 0x600057ad0; line 1456 (connection #0)
* Connection timed out after 300324 milliseconds
* multi_done
* stopped the pause stream!
* Closing connection 0
* The cache now contains 0 members
curl: (28) Connection timed out after 300324 milliseconds
$ /usr/bin/curl --version
curl 7.59.0 (x86_64-unknown-cygwin) libcurl/7.59.0 OpenSSL/1.0.2p
zlib/1.2.11 libidn2/2.0.4 libpsl/0.18.0 (+libidn2/2.0.2) libssh2/1.7.0
nghttp2/1.31.0
I also get an almost immediate 'failed to connect' notice on windows:
C:\>C:\UTIL\curl\curl.exe -v http://127.0.0.1:2/
* Trying 127.0.0.1...
* TCP_NODELAY set
* connect to 127.0.0.1 port 2 failed: Connection refused
* Failed to connect to 127.0.0.1 port 2: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 127.0.0.1 port 2: Connection refused
with either version of curl:
C:\>where curl
C:\UTIL\curl\curl.exe
C:\Windows\System32\curl.exe
Regards,
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-11-30 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 11:03 Basin Ilya
2018-11-30 19:49 ` Lee [this message]
2018-12-01 3:57 ` Brian Inglis
2018-12-01 9:51 ` Corinna Vinschen
2019-09-15 10:13 ` Basin Ilya
2020-11-12 15:35 ` basinilya
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=CAD8GWssBAH_KKXCC7jxTgCjS02KjXVb7LgkNvyriXJeE7cPSOg@mail.gmail.com \
--to=ler762@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).