From: Cameron Kaiser <spectre@stockholm.ptloma.edu>
Message-Id: <200106151333.GAA11640@stockholm.ptloma.edu>
Subject: [gopher] Re: Getting file info from an URI??
In-Reply-To: <20010615053931.D582@siva.heatdeath.org> from "em@nuel" at "Jun
 15, 1 05:39:31 am"
To: gopher@complete.org
Date: Fri, 15 Jun 2001 06:33:27 -0700 (PDT)
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> I'm don't really know the details about the gopher:// URL structure,
> but my impression is that it basically contains the full request line
> passed to the gopher server, so it could be something like
> "gopher://1/fooF+Ftext/html" to request the selector "1/foo" with
> Gopher+ as type text/html.  Getting the info is more complex than just
> appending "F!" to whatever comes after the //.

Perhaps use a URL-escaped %09 in there? Just guessing, never tried it.

> > Can one assume Gopher+ nowadays?
> 
> No.  There are lots of servers that aren't, including important ones
> like floodgap.

Yeah, it will be awhile before I get off my butt and put G+ into
Bucktooth.

-- 
----------------------------- personal page: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu
-- The fact that it works is immaterial. -- L. Ogborn -------------------------