Received: with LISTAR (v1.0.0; list gopher); Tue, 12 Feb 2002 14:55:22 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from tomts16-srv.bellnexxia.net (tomts16.bellnexxia.net [209.226.175.4]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 37D4B3B84D for ; Tue, 12 Feb 2002 14:55:22 -0500 (EST) Received: from [209.226.175.22] by tomts16-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020212195521.LHLB23163.tomts16-srv.bellnexxia.net@[209.226.175.22]> for ; Tue, 12 Feb 2002 14:55:21 -0500 From: Ralph Furmaniak To: gopher@complete.org Subject: [gopher] Re: Links to URL Date: Tue, 12 Feb 2002 14:55:21 EST MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20020212195521.LHLB23163.tomts16-srv.bellnexxia.net@[209.226.175.22]> X-archive-position: 444 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: sugaku@sympatico.ca Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher Nice solution, I'll try to implement it server-side. The only issue is item-types. For this to work, gopher0 clients must always be passed 'h', while it might be beneficial to pass gopher+ clients some other character. Since item-types do not mean that much if it is accessing a different protocol, how about if we say that all links to URLs have item-type 'h'. The only other alternative is to send a different character depending on the client. Also, for some bizarre perverse reason Internet Explorer cannot handle 'h' item types, and just presents everything as text. In computer circles, this is generally referred to as an 'uh-oh'. Yet most people will not be using IE, so it should not be a big problem.