Date: Wed, 23 Mar 94 13:27:31 CST
Message-Id: <9403231927.AA13066@boombox.micro.umn.edu>
From: "Mark P. McCahill" <mpm@boombox.micro.umn.edu>
To: dob@inel.gov, moore@cs.utk.edu, uri@bunyip.com
Subject: Re: gopher URLs (was Re: how to make progress ...)
In message <9403231515.AA01986@dewey.inel.gov> writes:
> 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.
Removing <tabs> would make it difficult to express Gopher+ URLs.
> 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.
The URL I proposed does cover Gopher+ and including +ASK forms.
> Mark McCahill is
> obviously the Gopher expert, but as a client author I have _some_
> experience to offer ...
>
The general solution is to not have clients do silly things like resolve a
URL if it points to the sendmail port (port 25). It probably make sence to
put that reccommendation into the URL document for all URLs, since this issue
can affect more access methods than just gopher. Sendmail is very trusting.
Mark P. McCahill
gopherspace engineer/University of Minnesota
mpm@boombox.micro.umn.edu
612 625 1300 (voice) 612 625 6817 (fax)