# Re: gopher URLs (was Re: how to make progress ...)

dob@inel.gov
Wed, 23 Mar 1994 08:15:51 -0700

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mark P. McCahill: "Re: gopher URLs (was Re: how to make progress ...)"
- Previous message: Tim Berners-Lee: "Re: how to make progress on the URL document"
- In reply to: Mark P. McCahill: "Re: how to make progress on the URL document"
- Next in thread: Mitra: "Re: how to make progress on the URL document"

    Date: Wed, 23 Mar 1994 08:15:51 -0700

    Message-Id: <9403231515.AA01986@dewey.inel.gov>

    From: dob@inel.gov

    To: moore@cs.utk.edu, uri@bunyip.com

    Subject: Re: gopher URLs (was Re: how to make progress ...)

    In-Reply-To: <199403230212.VAA08254@wilma.cs.utk.edu>

     <9403222119.AA06871@boombox.micro.umn.edu>

Keith Moore writes:
> shouldn't the gopher URL spec say something to the effect
> that the client shouldn't allow gopher URLs with embedded
> newlines or tabs?

The only problem is that some Gopher selectors have embedded tabs, for
instance most, if not all, Gopher+ selectors. I would say 'all Gopher+
selectors' but there might be an exception I'm not remembering ...

Anyway, eliminating tabs would not be a good thing. I've never seen a
Gopher selector with an embedded newline, except for the return from an ASK
block, and I suspect that UR* don't cover those. Mark McCahill is
obviously the Gopher expert, but as a client author I have _some_
experience to offer ...

Dave

- Next message: Mark P. McCahill: "Re: gopher URLs (was Re: how to make progress ...)"
- Previous message: Tim Berners-Lee: "Re: how to make progress on the URL document"
- In reply to: Mark P. McCahill: "Re: how to make progress on the URL document"
- Next in thread: Mitra: "Re: how to make progress on the URL document"