Date: Fri, 11 Jan 2002 08:02:51 -0800
From: Emanuel Borsboom <em@nuel.ca>
To: gopher@complete.org
Subject: [gopher] Re: Bucktooth and UMN gopher
Message-ID: <20020111080251.B13691@siva.heatdeath.org>
Mail-Followup-To: gopher@complete.org
References: <87k7uporj6.fsf@complete.org>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <87k7uporj6.fsf@complete.org>;
 from jgoerzen@complete.org on Fri, Jan 11, 2002 at 10:07:09AM -0500
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> When I use UMN gopher to hit floodgap.com, the root directory has one
> item:
> 
> "Main menu (non-gopher+)"

I remember I was trying to figure this out last year.  If I remember
correctly, it's because UMN gopher first attempts a Gopher+ request,
and falls back to a Gopher request if that fails.  Most Gopher(non-+)
servers will either fail, or return a standard Gopher directory when
given a Gopher+ request.  Floodgap's server notices that it's a
Gopher+ request and returns a menu that contains a single entry
which points to the root as a standard Gopher.

My interpretation of the Gopher and Gopher+ RFCs is that the correct
behaviour is for the client to make an empty (non-+) request when
initially connecting.  The resulting menu can contain Gopher+ entries.

-- 
Emanuel Borsboom
http://www.nuel.ca/