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

Michael Richardson <mcr@sandelman.ca> Sat, 02 February 2019 17:32 UTC

Return-Path: <mcr@sandelman.ca>
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 822971277CC for <tools-discuss@ietfa.amsl.com>; Sat, 2 Feb 2019 09:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 bjDZddPWF7Jt for <tools-discuss@ietfa.amsl.com>; Sat, 2 Feb 2019 09:32:46 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4A5126C7E for <tools-discuss@ietf.org>; Sat, 2 Feb 2019 09:32:46 -0800 (PST)
Received: from dooku.sandelman.ca (CPE788a207f397a-CMbc4dfb96bb50.cpe.net.cable.rogers.com [99.249.53.27]) by relay.sandelman.ca (Postfix) with ESMTPS id 458D81F42E; Sat, 2 Feb 2019 17:32:45 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1735F1101; Sat, 2 Feb 2019 12:32:22 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: Richard Barnes <richard.barnes@gmail.com>, tools-discuss <tools-discuss@ietf.org>
In-reply-to: <098AAA72-450A-4376-983F-57F0C667C212@tzi.org>
References: <CABcZeBPC8SsaFpRDarRDyHX0V6tW56QC_J56ziKAz_ya9fmy4A@mail.gmail.com> <CACB24MtLzNKNKwdNQbuna8HDbZR1NRuUJFsoRWYHUM+T_s6Rpw@mail.gmail.com> <098AAA72-450A-4376-983F-57F0C667C212@tzi.org>
Comments: In-reply-to Carsten Bormann <cabo@tzi.org> message dated "Sat, 02 Feb 2019 14:37:56 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 02 Feb 2019 12:32:22 -0500
Message-ID: <30833.1549128742@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/CI_pTL6aKYOmvuf7GGN-UGI66jQ>
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 17:32:50 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > 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).

+1

    > 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.

That would have also solved the problem, which I've also experienced.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [