Complete.Org: Mailing Lists: Archives: gopher: January 2001:
[gopher] Re: UMN gopher client weird behavior
Home

[gopher] Re: UMN gopher client weird behavior

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: UMN gopher client weird behavior
From: John Goerzen <jgoerzen@xxxxxxxxxxxx>
Date: 10 Jan 2001 12:02:58 -0500
Reply-to: gopher@xxxxxxxxxxxx

Cameron Kaiser <spectre@xxxxxxxxxxxxxxxxxxxx> writes:

> > 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 specific response is it that you send in this instance?

> 
> 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@xxxxxxxxxxxxxxxxxxxx
> -- Wagner's music is better than it sounds. -- Mark Twain 
> ---------------------
> 
> 
> 

-- 
John Goerzen <jgoerzen@xxxxxxxxxxxx>                       www.complete.org
Sr. Software Developer, Progeny Linux Systems, Inc.    www.progenylinux.com
#include <std_disclaimer.h>                     <jgoerzen@xxxxxxxxxxxxxxxx>



[Prev in Thread] Current Thread [Next in Thread]