Re: [Tools-discuss] Why does xml2rfc download over HTTP?

Carsten Bormann <cabo@tzi.org> Sat, 02 February 2019 13:38 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B03A128CE4 for <tools-discuss@ietfa.amsl.com>; Sat, 2 Feb 2019 05:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRSnaYhLMAEp for <tools-discuss@ietfa.amsl.com>; Sat, 2 Feb 2019 05:38:06 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E877A126C7E for <tools-discuss@ietf.org>; Sat, 2 Feb 2019 05:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x12DbvBP010373; Sat, 2 Feb 2019 14:38:02 +0100 (CET)
Received: from [192.168.217.106] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43sFQr6Pmzz1Br6; Sat, 2 Feb 2019 14:37:56 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CACB24MtLzNKNKwdNQbuna8HDbZR1NRuUJFsoRWYHUM+T_s6Rpw@mail.gmail.com>
Date: Sat, 02 Feb 2019 14:37:56 +0100
Cc: Eric Rescorla <ekr@rtfm.com>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 570807474.4031219-176c7f589621ebb445795129361448a9
Content-Transfer-Encoding: quoted-printable
Message-Id: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org>
References: <CABcZeBPC8SsaFpRDarRDyHX0V6tW56QC_J56ziKAz_ya9fmy4A@mail.gmail.com> <CACB24MtLzNKNKwdNQbuna8HDbZR1NRuUJFsoRWYHUM+T_s6Rpw@mail.gmail.com>
To: Richard Barnes <richard.barnes@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/t9gEgKfrnzQUc88vhRPtbkJolkc>
Subject: Re: [Tools-discuss] Why does xml2rfc download over HTTP?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Feb 2019 13:38:09 -0000

Right.  However, who ever fixes this should keep in mind that software installed on a laptop does not always have access to a good set of root certificates (the browser is likely to, but Python software may not have access to the browser set), so it would be useful to have an escape hatch of some kind (preferably through environment variables, so complex Makefiles don’t have to be touched).

Maybe adding a little bit of robustness to the download process (e.g., don’t cache it if it isn’t valid XML) would also help.

Grüße, Carsten


> On Feb 1, 2019, at 23:40, Richard Barnes <richard.barnes@gmail.com> wrote:
> 
> In particular, this seems to be the patch necessary to resolve the issue:
> 
> Index: trunk/cli/xml2rfc/parser.py
> ===================================================================
> --- trunk/cli/xml2rfc/parser.py	(revision 2965)
> +++ trunk/cli/xml2rfc/parser.py	(working copy)
> @@ -53,8 +53,6 @@
>                   no_network=None, network_locs= [
>                       'https://xml2rfc.ietf.org/public/rfc/',
>                       'https://xml2rfc.tools.ietf.org/public/rfc/',
> -                     'http://xml2rfc.ietf.org/public/rfc/',
> -                     'http://xml2rfc.tools.ietf.org/public/rfc/',
>                   ],
>                   rfc_number=None, options=base.default_options):
>          self.quiet = quiet if quiet != None else options.quiet
> 
> On Fri, Feb 1, 2019 at 5:08 PM Eric Rescorla <ekr@rtfm.com> wrote:
> Hi folks,
> 
> I recently went to build a draft and got a pile of errors about how the references didn't parse. Digging into things a bit, I discovered that the reference was the page from a captive portal on one of my flights. I'm not sure how this happened, but looking at xml2rfc, it appears that it tries HTTPS URIs and then HTTP URIs, which seems like it's going to have the wrong outcome in the situation where the captive portal blocks HTTPS and intercepts HTTP.
> 
> Is there a good reason to continue to allow HTTP URIs in the tool?
> 
> -Ekr
> 
> 
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org