Re: [Tools-discuss] File name truncation?

Adam Roach <adam@nostrum.com> Tue, 19 October 2010 14:19 UTC

Return-Path: <adam@nostrum.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 CEBAE3A6831 for <tools-discuss@core3.amsl.com>; Tue, 19 Oct 2010 07:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level:
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, SPF_PASS=-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 RLxV8SIbvoxr for <tools-discuss@core3.amsl.com>; Tue, 19 Oct 2010 07:19:46 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 42C533A6823 for <tools-discuss@ietf.org>; Tue, 19 Oct 2010 07:19:45 -0700 (PDT)
Received: from hydra-3.local (ppp-70-242-117-72.dsl.rcsntx.swbell.net [70.242.117.72]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9JELEfa067943 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 19 Oct 2010 09:21:15 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4CBDA95A.6050404@nostrum.com>
Date: Tue, 19 Oct 2010 09:21:14 -0500
From: Adam Roach <adam@nostrum.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: Henrik Levkowetz <henrik@levkowetz.com>
References: <4CBCF495.1080400@nostrum.com> <4CBDA6D9.2070305@levkowetz.com>
In-Reply-To: <4CBDA6D9.2070305@levkowetz.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.242.117.72 is authenticated by a trusted mechanism)
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:19:46 -0000

  On 10/19/10 09:10, Oct 19, Henrik Levkowetz wrote:
> 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.

Heh. I didn't actually select one over the other -- I'm just lazy enough 
that I don't bother digging through my bookmarks to get draft status. 
Instead, I type some substantial portion of the draft name in to Google, 
and click on the first link that comes up from tools.ietf.org. In this 
case, I landed on the rfcmarkup page instead of the cached page. I don't 
know how that particular link got picked up by Google...

If this starts to see heavy traffic, you might do a check in that script 
to see whether the Referer is one of the major search engines, and 
redirect to the cached version if it is.

/a