From: Cameron Kaiser <spectre@stockholm.ptloma.edu>
Message-Id: <200101100453.UAA12144@stockholm.ptloma.edu>
Subject: [gopher] Re: UMN gopher client weird behavior
In-Reply-To: <87k884ni0c.fsf@complete.org> from John Goerzen at "Jan 9,
 1 11:33:23 pm"
To: gopher@complete.org
Date: Tue, 9 Jan 2001 20:53:15 -0800 (PST)
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


> Jon Nelson (the guy behing pygopherd) has been asking me why UMN
> gopher is sending weird things to his server.  I did some checking and
> it looked to me that the TAB $ was a gopher+ism -- dunno why it would
> try to send that as the first thing ever, before it knows it's
> speaking to a gopher+ server.  Is this a bug?  Does anyone else do it?

David and I have discussed that behaviour before and we consider it a bug,
too. Bucktooth deals with it by simply sending a stock gopher+ response that
forces UMN-gopher to use regular gopher requests.

What's pygopherd?

> Next, he said he had observed it sending *spaces* and not a tab, or
> even a tab with no $.  Is this a bug?  It seems to me that it is.

Haven't seen this yet.

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- Wagner's music is better than it sounds. -- Mark Twain ---------------------