Re: Gopher (and searchable indexes)

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Gregory Kogut: "302 error"
• Previous message: Gisle Aas: "Re: patch for LWP 5.05 to make it play with both 5.003 and 5.003_20 + overload patch"
• In reply to: Bill Pollock: "Gopher (and searchable indexes)"

Bill Pollock <billp@statenet.com> writes:

> Perhaps this applies to searchable indexes in general.  I haven't seen
> all that many of them around, but this particular task calls for some
> interaction with one.
> 
> Anybody pulled this trick off?  When I go the standard w3 browser route
> and feed it a direct address (ie
> "gopher://gopher.server.wrld/.search?foo") UserAgent returns the
> standard searchable index message, rather than the result of the search.
> What the heck am I doing wrong?

I think the problem is that LWP follows the RFC1738 which says that
gopher URLs look like this:

3.4.1. Gopher URL syntax

   A Gopher URL takes the form:

      gopher://<host>:<port>/<gopher-path>

   where <gopher-path> is one of

       <gophertype><selector>
       <gophertype><selector>%09<search>


i.e. your URL should be something like

    gopher://gopher.server.wrld/.search%09foo

-- 
Gisle Aas <aas@sn.no>

• Next message: Gregory Kogut: "302 error"
• Previous message: Gisle Aas: "Re: patch for LWP 5.05 to make it play with both 5.003 and 5.003_20 + overload patch"
• In reply to: Bill Pollock: "Gopher (and searchable indexes)"