octave-bug-tracker
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL

From: Rik
Subject: [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL
Date: Tue, 28 Feb 2017 20:27:51 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 
Update of bug #50268 (project octave):

                  Status:                Wont Fix => Confirmed              
             Open/Closed:                  Closed => Open                   
                 Release:                   4.0.0 => 4.2.1                  

    _______________________________________________________

Follow-up Comment #10:

Re-opening this bug.  I can confirm this at the command line in a Windows XP
32-bit virtual machine.

Trying to read from the original address shows that it has been "temporarily"
redirected to an https address (SSL).  However, trying to read that new SSL
address results in some very scary error with the version of curl that is
shipped with Octave 4.2.1.


C:\Octave\Octave-4.2.1\bin>curl
"http://packages.octave.org/list_packages.php";
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>307 Temporary Redirect</title>
</head><body>
<h1>Temporary Redirect</h1>
<p>The document has moved <a
href="https://octave.sourceforge.io/list_packages.php";>here</a>.</p>
</body></html>

C:\Octave\Octave-4.2.1\bin>curl
"https://octave.sourceforge.io/list_packages.php";
curl: (35) schannel: next InitializeSecurityContext failed:
SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal
SSL/TLS alert is received (e.g. handshake failed). More detail may be
available in the Windows System event log.


Since this is only a problem on Windows, I'm adding John D. to the CC list. 
He handles issues with MXE which we use to cross-build Octave for windows. 
Looking in the log for the keyword curl I see


changeset:   4316:485c6d42ee42
user:        John D
date:        Wed Jan 04 08:32:24 2017 -0500
summary:     * src/curl.mk: update to 7.52.1

changeset:   4302:3d168da55e47
user:        John D
date:        Fri Dec 30 21:28:46 2016 -0500
summary:     disable instakll of docs

changeset:   4259:c5723e39a80e
user:        John D
date:        Tue Dec 13 10:48:19 2016 -0500
summary:     * src/curl.mk: update to v7.51.0

changeset:   4248:64063cd35eb2
user:        John D
date:        Tue Nov 15 20:18:19 2016 -0500
summary:     curl: enable winssl if compiling for windows

changeset:   4207:8a01ad4817a1
user:        John D
date:        Sun Sep 04 10:05:39 2016 -0400
summary:     curl: disable openssl check

changeset:   4167:892b4258cb8b
user:        John Donoghue
date:        Tue Jul 05 13:36:55 2016 -0400
summary:     curl: update to 7.49.1


Maybe winssl isn't as good as openssl (cset 4248)?



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50268>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
reply via email to
[Prev in Thread] Current Thread [Next in Thread]