Received: with LISTAR (v1.0.0; list gopher); Tue, 09 Jan 2001 22:36:55 -0600 (CST) Return-Path: Delivered-To: gopher@complete.org Received: from alexanderwohl.complete.org (localhost [127.0.0.1]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 177663B8F9; Tue, 9 Jan 2001 22:36:55 -0600 (CST) Received: by alexanderwohl.complete.org (Postfix, from userid 1000) id 7C2ABF23B; Tue, 9 Jan 2001 23:33:23 -0500 (EST) To: gopher@complete.org Subject: [gopher] UMN gopher client weird behavior From: John Goerzen Date: 09 Jan 2001 23:33:23 -0500 Message-ID: <87k884ni0c.fsf@complete.org> Lines: 17 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 78 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org X-list: gopher Hi, 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? 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. -- John -- John Goerzen www.complete.org Sr. Software Developer, Progeny Linux Systems, Inc. www.progenylinux.com #include