Message-ID: <003501c199f3$047e6720$5702010a@jgullicknb>
From: "Jason J. Gullickson" <mr@jasongullickson.com>
To: <gopher@complete.org>
References: 
 <004001c199e6$9fa9aeb0$5702010a@jgullicknb><878zb6tff6.fsf@complete.org><000d01c199e8$8ead77c0$5702010a@jgullicknb>
 <87zo3ms0gi.fsf@complete.org>
Subject: [gopher] Re: newbie server administrator question
Date: Thu, 10 Jan 2002 10:22:37 -0600
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


Ok, here's a weird twist,

I tested this using lynx instead of gopher, and I can access the file just
fine (?).

When I try to get to it using gopher, or Internet Explorer, it fails.

Gopher does nothing but blink the screen.

IE tries to access this URL:

gopher://unix1.inacom-msn.com%20/00/README%09%09%2B

the %20 in the URL is an encoded space, and if I remove it, IE reads the
file just fine.

Why would gopher put a space between the host and the first slash?

----- Original Message -----
From: "John Goerzen" <jgoerzen@complete.org>
To: <gopher@complete.org>; <mr@jasongullickson.com>
Sent: Thursday, January 10, 2002 9:13 AM
Subject: Re: [gopher] Re: newbie server administrator question


> "Jason J. Gullickson" <mr@jasongullickson.com> writes:
>
> > Here is the entire text I received from hitting "=" when the link was
> > selected (the file is the readme from the gopher tar file):
>
> OK, that looks correct, assuming that your hostname actually is
> unix1.inacom-msn.com.
>
> What exact error message do you get when you try to follow that link?
> Do you also get it if you use something like lynx?  (lynx
> gopher://localhost/ or lynx gopher://localhost/0/README)
>
> -- John
>
> --
> John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F
www.complete.org