public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ian Lambert via cygwin" <cygwin@cygwin.com>
To: <cygwin@cygwin.com>,  <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
Date: Thu, 15 Dec 2016 21:28:00 -0000	[thread overview]
Message-ID: <1138781101.3557942.1481836956476@mail.yahoo.com> (raw)
In-Reply-To: <1138781101.3557942.1481836956476.ref@mail.yahoo.com>


On Tue, 12/13/16, Brian Inglis wrote:

 Subject: Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
 To: cygwin@cygwin.com
 Date: Tuesday, December 13, 2016, 3:57 PM
 
 On 2016-12-13 11:43, Ian
 Lambert via cygwin wrote:
 > On Mon,
 12/12/16, Achim Gratz  wrote:
 >> Ian
 Lambert via cygwin writes:
 >>>
 Maybe a comparison of how wget handles authentication versus
 how
 >>> setup handles it could
 help?
 >> The problem is on your side
 and I cannot reproduce it. So that
 >>
 analysis (which I've asked for earlier) either comes
 from you or
 >> you'll have to wait
 until someone else can reproduce it. In any case,
 >> I've verified that setup.exe does
 ask for the user/password if it
 >>
 gets the required 407 error response from a proxy
 requiring
 >> authentication and then
 correctly uses that proxy for the remainder
 >> of the session.
 >
 The output from testing with wget and setup verbose is
 here:
 > https://cygwin.com/ml/cygwin/2016-12/msg00034.html
 > After skimming wget and setup sources, my
 guess is it has something
 > to do with
 "basic" versus NTLM authentication. I saw enough
 to know
 > setup source is not nearly as
 thoroughly commented as wget, and both
 >
 are too complicated for me. :D
 > Is there
 any chance of getting similar outputs from behind your
 > proxy, to look for differences with
 mine?
 
 Maybe your proxy is
 not properly handling unexpected User Agent or other 
 header strings from wget and setup. 
 Have you tried curl - curl often outputs only
 the HTTP message, and you 
 can then add
 options to generate the correct responses or handling. 
 Both curl and wget each support some user
 specified header addition and 
 modification
 options.
 
 Note that setup
 seems to require and support only Basic authentication 
 and does not process any negotiation, so if
 your proxy can or does not 
 fall back to
 support Basic authentication, only NTLM, you're
 hooped!
 
 Have you tried
 using apt-cyg or another alternate installer?
 I could suggest 
     https://github.com/BrianInglis/apt-cyg/raw/wget-non-verbose/apt-cyg
 ;^> 
 as it has been patched
 to handle installing dependencies and postinstall 
 scripts but does not (yet?) handle upgrades
 except by manually removing 
 and
 (re-)installing packages.
 
 You may have to do your setup and package
 downloads via apt-cyg, wget, 
 or IE to your
 packages directories and use setup to do installs from 
 there.
 
= = = 

At one time the proxy did seem to have user-agent requirements,
but lately it seems more forgiving, for wget and curl.

Thanks for your earlier curl and wget suggestions too. The output with
debug/verbose options is "interesting."

Yes, I've used apt-cyg downloads and offline setup/upgrade since about
last February. I'm using the latest version, with a small modification to
try to get "test" versions more reliably.

Oddly, trying to compare the outputs from different curl requests, with 
tkdiff, revealed that this script is no longer working for me. It worked
maybe 2 weeks ago. :/  It's always something.

--
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:[~2016-12-15 21:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1138781101.3557942.1481836956476.ref@mail.yahoo.com>
2016-12-15 21:28 ` Ian Lambert via cygwin [this message]
     [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] <15848438.1016337.1481543147254.ref@mail.yahoo.com>
2016-12-12 11:52 ` Ian Lambert via cygwin
2016-12-12 18:40   ` Achim Gratz
     [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=1138781101.3557942.1481836956476@mail.yahoo.com \
    --to=cygwin@cygwin.com \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --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).