To: gopher@complete.org
Subject: [gopher] Re: Bucktooth and UMN gopher
References: <200201120223.SAA09148@stockholm.ptloma.edu>
From: John Goerzen <jgoerzen@complete.org>
Date: 12 Jan 2002 11:45:15 -0500
In-Reply-To: <200201120223.SAA09148@stockholm.ptloma.edu>
Message-ID: <873d1bh61w.fsf@complete.org>
Lines: 29
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


The thing is, though, that it is perfectly valid to reply to a Gopher+
request with a Gopher0 menu.  You could reply to UMN gopher with the
regular gopher0 menu that you reply to other things with.

That said, I'll take a look at the behavior for the next release.

-- John

Cameron Kaiser <spectre@stockholm.ptloma.edu> writes:

> > 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.
> 
> Correct. TTBOMK, only UMN gopher has this behaviour, and the patch I put
> in Bucktooth is specially for it (and any others that might be lurking).
> 
> -- 
> ----------------------------- personal page: http://www.armory.com/~spectre/ --
>  Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
> -- I'm a dyslexic amateur orthinologist. I just love word-botching. -----------
> 

-- 
John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F    www.complete.org