From: "Ian Lambert via cygwin" <cygwin@cygwin.com>
To: <cygwin@cygwin.com>, Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
Date: Mon, 12 Dec 2016 11:52:00 -0000 [thread overview]
Message-ID: <15848438.1016337.1481543147254@mail.yahoo.com> (raw)
In-Reply-To: <15848438.1016337.1481543147254.ref@mail.yahoo.com>
On Thu, 12/8/16, Achim Gratz wrote:
Subject: Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
To: cygwin@cygwin.com
Date: Thursday, December 8, 2016, 2:22 PM
Ian Lambert writes:
> The proxy gives the 407 error, based on
some testing
> with wget -d. Even without
providing user/password, it works
>
around half the time, for wget. Below are some debug output
from setup,
> and debug output from wget
testing, which shows the 407 error.
It took some time to get to it, but I've
tested setup.exe using an NTLM authenticating
proxy @work today and it does exactly what it
is supposed to do (pop up
a dialog box
asking for the user name and password, then authenticate
to
the proxy and use it for the rest of the
session).
So your problem
still seems to be some misconfiguration on the proxy
side that causes communication with setup.exe
to fail.
= = =
You can call it "misconfiguration." I can call it
"different" configuration than setup assumes.
The point remains: other programs, like wget,
consistently work OK, without popups, when given
proxy username and password in either .bashrc
or .wgetrc, and I am sure they were not customized
for this proxy.
Maybe a comparison of how wget handles
authentication versus how setup handles it
could help?
> Defaulting to
empty mirror list
> site: ftp://mirrors.kernel.org/sourceware/cygwin/
Err… could it be that your
proxy isn't actually of functioning as an FTP
proxy? How about using a HTTP mirror
instead?
= = =
No. Wget works OK with either type. HTTP mirror
has been tried with setup, and also does not work.
From previous post, setup fails to retrieve mirrors.lst,
with an HTTP, before failing to retrieve setup.ini.
Again, wget can retrieve these consistently OK
when given username and password.
net: Proxy
Cached mirror list unavailable
get_url_to_membuf http://cygwin.com/mirrors.lst
getUrlToStream http://cygwin.com/mirrors.lst
getUrlToStream failed!
get_url_to_membuf failed!
next parent reply other threads:[~2016-12-12 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15848438.1016337.1481543147254.ref@mail.yahoo.com>
2016-12-12 11:52 ` Ian Lambert via cygwin [this message]
2016-12-12 18:40 ` Achim Gratz
[not found] <1138781101.3557942.1481836956476.ref@mail.yahoo.com>
2016-12-15 21:28 ` Ian Lambert via cygwin
[not found] <1514592420.2041696.1481654586533.ref@mail.yahoo.com>
2016-12-13 18:47 ` Ian Lambert via cygwin
2016-12-13 20:57 ` Brian Inglis
[not found] <2128275392.6182492.1480962659006.ref@mail.yahoo.com>
2016-12-05 18:31 ` Ian Lambert
2016-12-08 19:23 ` Achim Gratz
[not found] <282225090.3963609.1480612234263.ref@mail.yahoo.com>
2016-12-01 17:13 ` Ian Lambert
2016-12-01 18:08 ` Brian Inglis
2016-12-01 20:03 ` Achim Gratz
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=15848438.1016337.1481543147254@mail.yahoo.com \
--to=cygwin@cygwin.com \
--cc=Stromeko@nexgo.de \
--cc=ian.lambert_42@yahoo.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).