Re: [Tools-discuss] File name truncation?

Henrik Levkowetz <henrik@levkowetz.com> Tue, 19 October 2010 14:09 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD49D3A6831 for <tools-discuss@core3.amsl.com>; Tue, 19 Oct 2010 07:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level:
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htLUn5ecdy-e for <tools-discuss@core3.amsl.com>; Tue, 19 Oct 2010 07:09:47 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id B6E393A680A for <tools-discuss@ietf.org>; Tue, 19 Oct 2010 07:09:46 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:62473 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1P8Ctd-0006C9-Nr; Tue, 19 Oct 2010 16:10:52 +0200
Message-ID: <4CBDA6D9.2070305@levkowetz.com>
Date: Tue, 19 Oct 2010 16:10:33 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
References: <4CBCF495.1080400@nostrum.com>
In-Reply-To: <4CBCF495.1080400@nostrum.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: adam@nostrum.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: Tools Team Discussion <tools-discuss@ietf.org>
Subject: Re: [Tools-discuss] File name truncation?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 19 Oct 2010 14:09:48 -0000

Hi Adam,

On 2010-10-19 03:29 Adam Roach said:
>   When I go to 
> "http://tools.ietf.org/rfcmarkup?topmenu=true&doc=draft-roach-sip-http-subscribe" 
> and then click on "tracker", it gives me an error. The problem seems to 
> be that it is trying to open 
> "https://datatracker.ietf.org/doc/draft-roach-sip-http-subscr/" instead 
> of "https://datatracker.ietf.org/doc/draft-roach-sip-http-subscribe/".
> 
> Is there some kind of very small limit on file names in the tools database?

No, you're just using the raw tool without providing quite the expected input
format.  That particular invocation expects the doc parameter to contain the
revision number.

If you instead use the path

  http://tools.ietf.org/html/draft-roach-sip-http-subscribe

you'll get a better result, as that interface goes to some length to produce
correct parameters to provide to the rfcmarkup tool which does the actual
conversion.  The pages are also cached in order to load the servers less and
produce results faster (but in some cases (maybe yours?) the caching is
undesirable, of course).  Is there any particular reason why you prefer to use
the direct /rfcmarkup? invocation?  If this has started to get substantial use,
I should understand why, and see if something needs to be changed in order to
support the use better.


Best,

	Henrik