[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pkg install -forge issues?

From: Nicholas Jankowski
Subject: Re: pkg install -forge issues?
Date: Fri, 16 Dec 2016 13:31:18 -0500

On Fri, Dec 16, 2016 at 1:19 PM, Mike Miller <address@hidden> wrote:
On Fri, Dec 16, 2016 at 12:44:49 -0500, Nicholas Jankowski wrote:
> On Fri, Dec 16, 2016 at 12:18 PM, Mike Miller <address@hidden> wrote:
> > Does this work
> >
> >   [txt, status] = urlread ("")
> >
> >
> >>  [txt, status] = urlread ("")
> txt =
> status = 0
> ? Does it work in your web browser of choice?
> >
> >
> going to
> redirects to
> which loads fine.
> > Is the Windows distribution unable to cope with the sourceforge ssl
> > certs?
> >
> don't think so.  have no problem manually downloading the package which is
> pulling from

I meant the Windows distribution of Octave, not the Windows OS in

The error with urlread seems to confirm that it can't read the URL, but
without any details about why. I'm only guessing this is because of the
ssl certs. Can you successfully read http URLs but not any https URLs,
taking redirects into account?

Here's a sample set of http URLs that do not automatically redirect to

  urlread ("")
  urlread ("")
  urlread ("")

Do these work for you? Do they work with https?

all three return work with http but not https


And circling back to sourceforge, does this URL work

  urlread ("")

versus this one

  urlread ("")

same. http works, https returns 0
Does the Octave bin directory include the curl executable?

yes. there is a curl.exe and a curl-config

Can you try
any failing URLs with "curl -v" and see if any errors or other details
can help indicate what the problem is?

curl -v ""


curl -v ""


C:\Octave\octave-4.2.0-w64\bin>curl -v ""
* Rebuilt URL to:
* timeout on name lookup is not supported
*   Trying
* Connected to ( port 443 (#0)
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification failed. CAfile: none CRLfile: none
* Closing connection 0
curl: (60) server certificate verification failed. CAfile: none CRLfile: none
More details here:

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

Is that it?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]