Received: with ECARTIS (v1.0.0; list gopher); Wed, 17 Jul 2002 16:31:56 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "*.myrealbox.com", Issuer "Thawte Server CA" (not verified)) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 516373B8DF for ; Wed, 17 Jul 2002 16:31:50 -0500 (EST) Received: from transa.aquarius.null aangel@smtp-send.myrealbox.com [24.171.111.62] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare via secured & encrypted transport (TLS); Wed, 17 Jul 2002 15:31:14 -0600 Subject: [gopher] Re: PyGopherd + gophermap From: "Aaron J. Angel" To: gopher@complete.org In-Reply-To: <20020717211427.GE13625@complete.org> References: <1026816676.25554.3.camel@transa.aquarius.null> <20020717211427.GE13625@complete.org> Content-type: text/plain X-Mailer: Ximian Evolution 1.0.8 Date: 17 Jul 2002 16:30:55 -0500 Message-Id: <1026941463.1379.25.camel@transa.aquarius.null> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-archive-position: 645 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: aangel@myrealbox.com Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Wed, 2002-07-17 at 16:14, John Goerzen wrote: > > On Tue, Jul 16, 2002 at 05:51:15AM -0500, Aaron J. Angel wrote: > > > > What's up with the gophermap support in PyGopherd? Bucktooth's > > gophermap files are slightly more intuitive than the ones PyGopherd seem > > to support (e.g.: info lines have no tabs in bucktooth, which doesn't > > seem to work with PyGopherd)...and there was something else, but I can't > > remember what. > > If you could send me a sample gophermap file and a description of what > Pygopherd does wrong, I'll be pleased to fix it. For example, the following in bucktooth: Info test blah blah blah with no tabs whatsoever, is turned into an i-entry. PyGopherd requires something like this (F being the tab seperator): iInfo test blah blah blahF I think there may have been something else that seemed broken, but I'm not sure...if I remember (I likely won't), I'll tell ya. > > Also, is there a way to allow the use of type tags in HTTP URIs? It'd > > be most useful for Gopher/Web sites (I suppose I could simply to /, > > but that seems a bit crude). > > Hmm, I'm not sure I understand the question. Are you referring to Pygopherd > as a HTTP server, or to links from Gopherspace to HTTP-space? As an HTTP server. For example, if you have an HTML link to /, it works fine using HTTP. But, say you're browser supports gopher, and you try the same link, there's no type specified, so it fails. However, if you change it to /0/ or whatever, it works with Gopher, but not with HTTP. -- Aaron J. Angel -- Attached file included as plaintext by Ecartis -- -- File: signature.asc -- Desc: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQA9NeIPKjh8Do+vm9ARAhCNAKDpw4Iqyy4/JbGZtX5ucErjG8rgigCfTECq NTzI4Tbku399z/wRk0LIK+8= =f7E1 -----END PGP SIGNATURE-----