[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: |
A.R. Burgers |
Subject: |
[Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL |
Date: |
Mon, 13 Feb 2017 13:37:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #3, bug #50268 (project octave):
and I noticed that, when working with a proxy, environment variable
https_proxy must be set following the transition to https, http_proxy only is
not sufficient (it is sufficient for wget, not for curl).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50268>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Michele, 2017/02/09
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Rik, 2017/02/09
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Mike Miller, 2017/02/10
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL,
A.R. Burgers <=
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Nicholas Jankowski, 2017/02/27
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Michele, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Nicholas Jankowski, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Michele, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Mike Miller, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Michele, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Rik, 2017/02/28
- [Octave-bug-tracker] [bug #50268] get_forge_pkg: could not read URL, Nicholas Jankowski, 2017/02/28