Received: with LISTAR (v1.0.0; list gopher); Fri, 15 Jun 2001 11:35:49 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from stockholm.ptloma.edu (stockholm.ptloma.edu [199.106.86.50]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 72C483B80B for ; Fri, 15 Jun 2001 11:35:49 -0500 (EST) Received: (from spectre@localhost) by stockholm.ptloma.edu (8.9.1/8.9.1) id JAA10528 for gopher@complete.org; Fri, 15 Jun 2001 09:39:01 -0700 From: Cameron Kaiser Message-Id: <200106151639.JAA10528@stockholm.ptloma.edu> Subject: [gopher] Re: Getting file info from an URI?? In-Reply-To: <992619438.769.0.camel@Pflipp> from Stefan Rieken at "Jun 15, 1 05:37:17 pm" To: gopher@complete.org Date: Fri, 15 Jun 2001 09:39:01 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-archive-position: 180 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: spectre@stockholm.ptloma.edu 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 > > Well, this isn't *really* true. The first character is always the item type. > > Well, that may be common current practice, but that's not quite required > behaviour from either the Gopher or the Gopher+-standards, is it? > > If so, determining the file type by looking at the first character may > now work in 99% of the cases, until someone develops a "new, improved" > Gopher server which uses different selectors that gets popular, after > which maybe only in 70% of the cases this will work. From the browser's point of view, it is. That very first character is never sent to the server, but is intercepted by the web browser to tell it how to handle the data. For example, a URL like gopher://floodgap.com/1/v2/ tells the browser this is item type 1, a gopher menu, and it sends /v2/ to the server. Some servers like getting a second copy of the item type, so they'll have gopher://slacker.invalid/11/v2/ but the browser will still take that first '1' off and send 1/v2/ to the server, so you can still count on getting that item type. > > True; a Mac HFS gopher server, of which there are some, uses ":". > > Makes me wonder: how do webbrowsers translate these server's selector to > an URI? Does it leave in the ":" or replace it with a "/"? Just curious. They leave it in (at least Netscape seems to). Remember that everything in a gopher menu is a fully-qualified "path" so the browser doesn't have to worry about what a path delimiter is and isn't -- it just passes the entire selector along and lets the server deal with it. -- ----------------------------- personal page: http://www.armory.com/~spectre/ -- Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu -- The first duty of a revolutionary is to get away with it. -- Abbie Hoffman -