public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sharuzzaman Ahmat Raslan <sharuzzaman@gmail.com>
To: cygwin@cygwin.com, Wes.Barris@cobb-vantress.com
Cc: Yaakov Selkowitz <yselkowitz@cygwin.com>
Subject: Re: Re: Curl-7.64.1-1 not returning any data
Date: Thu, 23 May 2019 23:13:00 -0000	[thread overview]
Message-ID: <CAK+zucnHNhVpXnxudGnFZVgVuEohRUT98k=yYCVUw1LoZj+wrw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR17MB2300C9B7AD6D78E0A9B61A5ED8010@DM6PR17MB2300.namprd17.prod.outlook.com>

http://www.cygwin.com/acronyms/

*WFM* Works For Me. Also IWFM <http://www.cygwin.com/acronyms/#IWFM> (or
WJFFM <http://www.cygwin.com/acronyms/#WJFFM>, for extra emphasis)
*BLODA* Big List Of Dodgy Apps. A list
<https://cygwin.com/faq/faq.html#faq.using.bloda> of applications that
interfere with the normal working of Cygwin by intrusively injecting
themselves in the system call chain. First used on the list
<https://cygwin.com/ml/cygwin/2007-09/msg00014.html> by Dave Korn.

https://cygwin.com/faq/faq.html#faq.using.bloda

As you have tried to reinstall Cygwin, I think the issue could be within
Windows itself. Please check if you have any tools listed in the BLODA, or
something that is similar in function (eg. intercept network connection)

Thank you



On Fri, May 24, 2019 at 3:51 AM Barris, Wes <Wes.Barris@cobb-vantress.com>
wrote:

> On Thu, 2019-05-23 at 14:22 +0000, Barris, Wes wrote:
> >> About two months ago curl stopped working in our cygwin installations.
> >> It is unclear what has changed apart from periodic cygwin and windows
> >> updates.  I have tried re-installing cygwin.  I have tried installing
> >> cygwin on a different computer.  The result is the same -- not
> working.  Curl does work as expected on our Linux systems.
> >> Invoke-WebRequest (PowerShell) continues to work even on the same
> >> systems where curl (Cygwin) does not.  Here is an example:
> >
> >WFM; BLODA?
>
> TFTTTTTIATC! (EWaS)
>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the addressee. If you are not the intended addressee,
> then you have received this email in error and any use, dissemination,
> forwarding, printing, or copying of this email is strictly prohibited.
> Please notify us immediately of your unintended receipt by reply and then
> delete this email and your reply. Cobb-Vantress, Inc. and its subsidiaries
> and affiliates will not be held liable to any person resulting from the
> unintended or unauthorized use of any information contained in this email
> or as a result of any additions or deletions of information originally
> contained in this email.
>
> --
> 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
>
>

-- 
Sharuzzaman Ahmat Raslan

--
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

      reply	other threads:[~2019-05-23 23:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 14:23 Barris, Wes
2019-05-23 15:44 ` Yaakov Selkowitz
2019-05-23 19:51   ` Barris, Wes
2019-05-23 23:13     ` Sharuzzaman Ahmat Raslan [this message]

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='CAK+zucnHNhVpXnxudGnFZVgVuEohRUT98k=yYCVUw1LoZj+wrw@mail.gmail.com' \
    --to=sharuzzaman@gmail.com \
    --cc=Wes.Barris@cobb-vantress.com \
    --cc=cygwin@cygwin.com \
    --cc=yselkowitz@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).