Re: [xml2rfc] 302 error for RFC0793

Carsten Bormann <cabo@tzi.org> Fri, 17 May 2019 17:08 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1CA1201C5 for <xml2rfc@ietfa.amsl.com>; Fri, 17 May 2019 10:08:24 -0700 (PDT)
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 Wjd22I56jtVF for <xml2rfc@ietfa.amsl.com>; Fri, 17 May 2019 10:08:22 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E8F01201E5 for <xml2rfc@ietf.org>; Fri, 17 May 2019 10:08:22 -0700 (PDT)
Received: from [192.168.217.106] (p54A6CC75.dip0.t-ipconnect.de [84.166.204.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 455F9b5X29z108W; Fri, 17 May 2019 19:08:19 +0200 (CEST)
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: <0B0A6136-2E2E-4873-94AE-37E63BE5EFC0@bangj.com>
Date: Fri, 17 May 2019 19:08:19 +0200
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 579805696.939916-bafda71e473118879af63b3f86032979
Content-Transfer-Encoding: quoted-printable
Message-Id: <6EAA4AFD-6352-4597-A68F-D57227E2822F@tzi.org>
References: <0B0A6136-2E2E-4873-94AE-37E63BE5EFC0@bangj.com>
To: Tom Pusateri <pusateri@bangj.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/-MWM3vmeuAOqDUChAzRmDN49WSs>
Subject: Re: [xml2rfc] 302 error for RFC0793
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 17:08:24 -0000

On May 17, 2019, at 18:24, Tom Pusateri <pusateri@bangj.com> wrote:
> 
> Verbose version shows a 302 error. I’m sure the leading 0 was required at one point.

In kramdown-rfc, a while ago I changed the default hostname from xml2rfc.ietf.org to xml2rfc.tools.ietf.org to avoid those 302s.

(There is nothing wrong with the leading zero in RFC0793.)

Grüße, Carsten