IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Fri, 01 February 2019 22:08 UTC

Return-Path: <ekr@rtfm.com>
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 A13DD130EC5 for <tools-discuss@ietfa.amsl.com>; Fri, 1 Feb 2019 14:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level:
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 gyEIcT7IoF_r for <tools-discuss@ietfa.amsl.com>; Fri, 1 Feb 2019 14:08:30 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C48F5130EBE for <tools-discuss@ietf.org>; Fri, 1 Feb 2019 14:08:29 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id x85-v6so7134310ljb.2 for <tools-discuss@ietf.org>; Fri, 01 Feb 2019 14:08:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=dtW5vx8FSW5Am/rMTxeM1HoAVUnmyoepqd1LyXlf0rA=; b=09R6U0iq2g+fPNZY38mRQhLhJ9gZhvsvO1tMq62xPXRwnlsEBypdYPhuhlDahLaZe7 xJxm8Nfnp8KS/sHWOQ0/N9ckBgzx4TjCOtj95LfkncJ8V4/kGEQXQo54An7nzu7RBvgO fCs3g3fkjkjPpnFhua5I36y9ZqWnEl0F6QhnFZtK8O6CR5Yyk10n/djj9r6OadKMRmrf /QjIL/CI0rnv8HWJTV7lYCQUWke5GS+KEO/HYB33owszm4Gaca2RnAvfwkKvKpK63tUY ifzN0ra103TOxZx0B4YxHXlhtENIu2+HVc4o2SoPqj1ZIJbHqH9xwAcmcUrDzAVu2sD0 Qyow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dtW5vx8FSW5Am/rMTxeM1HoAVUnmyoepqd1LyXlf0rA=; b=D/ROe+Vf0cftcyIj33c0vfGpTsW7aawNBtvhJMlRJFnZwWZ+H7e8G32oA0Mgq4LQ4u cmlianeAA0FrGGj3ST31RF0qoVfX2D/NGH3iTTyTKXOkPg3fbktkfbVY1WLrHG8lYJ18 Ufb1tnqmHXI6ixCJ3NwWPCBa/AFTb/09r+0jJfeIokltJ3565Q5xiRYc6tTQN0Xxa5L/ LPrzX+o395TbS92BmTPAqwbNcZFcsgN4sRglknWWRMbEpwJ/ILqtEy6Fh/QwCYC/H/UL hdHrqp7cHUPxYnYOFj9CU4xDkqPRWPm6VXJRY4IqpiF+AEtfDWscEDMTsWfH8YsKNPOD Kt6w==
X-Gm-Message-State: AJcUukcW5XaAyqlk24b81Wfo2wvTqlXYWpIMfFoJt59+lGix3vQyM062 kFv3zWIQRw7LhAjrWuLzLvPV7hP2hwwDkDF9rj9DX7snim4=
X-Google-Smtp-Source: ALg8bN6k/XRR+SZTfRwQTuHO/bLq98whCnA8ES/rueuNmk20LXCTVt6HvH5TztcHjodjClmN5nPs8WFF25RDeIYnVQw=
X-Received: by 2002:a2e:5dd9:: with SMTP id v86-v6mr32663081lje.86.1549058907467; Fri, 01 Feb 2019 14:08:27 -0800 (PST)
MIME-Version: 1.0
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 01 Feb 2019 14:07:51 -0800
Message-ID: <CABcZeBPC8SsaFpRDarRDyHX0V6tW56QC_J56ziKAz_ya9fmy4A@mail.gmail.com>
To: tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ea8b120580dc611a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/lrJNxCc4vuKU2Oa0y6lZgGjifTs>
Subject: [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: Fri, 01 Feb 2019 22:08:32 -0000

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

v2.23.0 | Report a Bug | By Email