public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin x86 setup issue:Can't connect to (null):80
Date: Wed, 25 Oct 2017 21:35:00 -0000	[thread overview]
Message-ID: <0b763f3f-7157-ed7d-2c5d-d65c1e2afa1b@SystematicSw.ab.ca> (raw)
In-Reply-To: <3F47E06D-EB50-4BCC-992E-1D8EF5E4F314@apple.com>

On 2017-10-25 13:52, Lynn Lin wrote:
>> On 2017-10-24,9:23,Jon Turney <jon.turney@dronecode.org.uk> wrote:
>>> On 15/10/2017 02:39, Lynn Lin wrote:
>>> we are using our internal cygwin mirror(xx.xx.xx.xx:8000) and when we
>>> setup setup-x86.exe, it is in cygwin setup ui, show downloading and
>>> connecting, finally it show download incomplete, through the log, it
>>> shows:
>>> Can’t connect to (null):80 ,
>>> get_url_to_file failed !
>>> any idea about this issue?
>>
>> I thought perhaps setup couldn't handle a nonstandard port, but in my 
>> testing, that seems to work ok.
>>
>> Can you provide a /var/log/setup.log.full showing this problem? (censoring 
>> any details you don't want to make public)
> Thanks, no log available is right now
> We are using golang net/http to setup a http file share in OSX and looks it 
> can’t handle “//“ for Cygwin packages path like http://xx.xx/cywin//x86/xx> And when we try python simple http server package and it works
Remove the extra slash above ...//... between cygwin and x86:
	http://cygwin.mirror.local:port/cygwin/x86/...
	                                      ^
as some Internet libraries and/or servers do not handle that by removing the
extra slash.

Best to paste the actual log content into the email or attach the log as text.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2017-10-25 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-15  1:39 Lynn Lin
2017-10-24 13:23 ` Jon Turney
2017-10-25 19:52   ` Lynn Lin
2017-10-25 21:35     ` Brian Inglis [this message]
2017-10-26 14:35     ` Andrey Repin
2017-10-26 15:52 Fergus
2017-10-26 20:40 ` Jon Turney
2017-10-27 13:48   ` Jon Turney
2017-10-27 14:31 Fergus

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=0b763f3f-7157-ed7d-2c5d-d65c1e2afa1b@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).