From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#19840: "Bad uri header component" when downloading from gitorious.org Date: Thu, 19 Feb 2015 03:42:24 -0500 Message-ID: <87ioeygumn.fsf@netris.org> References: <874mqsns2h.fsf@mango.localdomain> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51692) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOMhS-0002ye-De for bug-guix@gnu.org; Thu, 19 Feb 2015 03:43:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YOMhL-0000Ms-3V for bug-guix@gnu.org; Thu, 19 Feb 2015 03:43:10 -0500 Received: from debbugs.gnu.org ([140.186.70.43]:57100) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOMhL-0000Mm-0Z for bug-guix@gnu.org; Thu, 19 Feb 2015 03:43:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YOMhK-0008C1-Bw for bug-guix@gnu.org; Thu, 19 Feb 2015 03:43:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <874mqsns2h.fsf@mango.localdomain> (Ricardo Wurmus's message of "Wed, 11 Feb 2015 20:53:10 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ricardo Wurmus Cc: 19840-done@debbugs.gnu.org Ricardo Wurmus writes: > Downloading archives from gitorious fails: > > ~/dev/guix $ ./pre-inst-env guix download https://gitorious.org/lv2-synths/lv2-mdametapiano/archive/0.0.1.tar.gz > starting download of `/tmp/guix-file.gqYdZs' from `https://gitorious.org/lv2-synths/lv2-mdametapiano/archive/0.0.1.tar.gz'... > ERROR: Bad uri header component: /lv2-synths/lv2-mdametapiano/archive/ceb5345396425ad526be34c79eae2b4dfe886d5b.tar.gz Guile's parsing and validation of HTTP "Location" headers was based on the now obsolete RFC 2616 section 14.30, which required it to be an absolute URI. However, RFC 7231 section 7.1.2 allows it to be any URI reference, which can include relative URIs. This will be fixed in Guile 2.0.12. Additionally, the possibility of HTTP redirects to relative URIs requires us to determine the target URI based on a relative URI and base URI, using the algorithm described in RFC 3986 section 5.2.2. I just pushed commit 04dec194d8 to master which resolves both of these issues. I'm closing this bug now. Thanks! Mark