Re: Gopher support in X Mosaic, cosmetic suggestion
Martin Hamilton <M.T.Hamilton@lut.ac.uk>
Message-id: <9306131032.AA10222@dxmint.cern.ch>
Subject: Re: Gopher support in X Mosaic, cosmetic suggestion
To: Guido.van.Rossum@cwi.nl
Date: Sun, 13 Jun 1993 11:36:28 +0100 (BST)
Cc: www-talk@nxoc01.cern.ch
In-reply-to: <9306131023.AA04219=guido@voorn.cwi.nl> from "Guido.van.Rossum@cwi.nl" at Jun 13, 93 12:23:40 pm
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 948
From: Martin Hamilton <M.T.Hamilton@lut.ac.uk>
Sender: M.T.Hamilton@lut.ac.uk
Thus spake Guido :
/ Huh? As far as I know there is no gateway involved when www clients
/ like XMosaic access Gopher servers: support for the Gopher protocol is
/ built in the client. (There may be a gateway in existence
/ nevertheless, but it must be intended only for access through clients
/ that don't know the Gopher protocol yet.)
I think he's talking about the NCSA httpd - see below - Martin
OVERVIEW OF GOPHER SUPPORT
--------------------------
As of beta release .3, this server will automatically generate
HTML listings of a gopher directory without going through gopherd.
This means that . files which are links are processed, and .cap files
are processed. Any request which begins with /gopher-data will be
considered a gopher request if gopher is turned on. Therefore, mapping
/gopher-data to the location of your server's data will allow you to
access /gopher-data and get a gopher listing in return.