Gopher (protocol)

Template:IPstack The Gopher protocol is a TCP/IP Application layer protocol designed for distributing, searching, and retrieving documents over the Internet, and was a predecessor, and later, an alternative to the World Wide Web. The protocol offers some features not natively supported by the Web and imposes a much stronger hierarchy on information stored on it. Its text menu interface is well-suited to computing environments that rely heavily on remote computer terminals, common in universities at the time of its creation in 1991 until 1993.

Origins

The original Gopher system was released in late spring of 1991 by Mark McCahill, Farhad Anklesaria, Michael Guevara de Jesus, Paul Lindner, Daniel Torrey, Bob Alberti, and Terry Nickman of the University of Minnesota. Its central goals were:

• A file-like hierarchical arrangement that would be familiar to users
• A simple syntax
• A system that can be created quickly and inexpensively
• Extending the file system metaphor to include things like searches

The source of the name "Gopher" is claimed to be threefold:

1. Users instruct it to "go for" information
2. It does so through a web of menu items analogous to gopher holes
3. The sports teams of the University of Minnesota are the Golden Gophers

Gopher combines document hierarchies with collections of services, including WAIS, the Archie and Veronica search engines, and gateways to other information systems such as ftp and Usenet.

The general interest in Campus-Wide Information Systems (CWISs) in higher education at the time, and the ease with which a Gopher server could be set up to create an instant CWIS with links to other sites' online directories and resources were the factors contributing to Gopher's rapid adoption. By 1992, the standard method of locating someone's e-mail address was to find their organization's CCSO nameserver entry in Gopher, and query the nameserver.

The exponential scaling of utility in social networked systems (Reed's law) seen in Gopher, and then the Web, is a common feature of networked hypermedia systems with distributed authoring. In 1993–1994, Web pages commonly contained large numbers of links to Gopher-delivered resources, as the Web continued Gopher's embrace and extend tradition of providing gateways to other services.^{[citation needed]}

Stagnation

The World Wide Web was in its infancy in 1991, and Gopher services quickly became established. By the late 1990s, Gopher had largely ceased expanding. Several factors contributed to Gopher's stagnation:

• In February 1993, the University of Minnesota announced that it would charge licensing fees for the use of its implementation of the Gopher server. As a consequence of this some users suspected that a licensing fee would also be charged for independent implementations. In contrast, no such limitation has yet been imposed on the World Wide Web. The University of Minnesota eventually re-licensed its Gopher software under the GNU GPL.
• Gopher Client functionality was quickly duplicated by early Web browsers, such as Mosaic. Furthermore, the user friendliness of the World Wide Web, with its integration of text and graphics, made Gopher less appealing.
• Gopher has an inflexible structure when compared to the free-form HTML of the Web. With Gopher, every document has a defined format and type, and the typical user must navigate through a single server-defined menu system to get to a particular document.

Availability of Gopher today

Recently, there have been attempts to revive the use of Gopher. One such attempt is the Overbite project, a Firefox extension that adds better support for the protocol to Firefox.

As of 2008, there are approximately 125 gopher servers indexed by Veronica-2, a slow growth from 2007 when there were fewer than 100. Many of them are owned by universities in various parts of the world. Most of them are neglected and rarely updated except for the ones run by enthusiasts of the protocol. A handful of new servers are set up every year by hobbyists — 30 have been set up and added to Floodgap's list since 1999 and possibly some more that haven't been added. Due to the simplicity of the Gopher protocol, setting up new servers or adding Gopher support to browsers is often done in a tongue-in-cheek way, principally on April Fools' Day

Some have suggested that the bandwidth-sparing simple interface of Gopher would be a good match for mobile phones and Personal digital assistants (PDAs), but so far, Wireless Markup Language (WML)/Wireless Application Protocol (WAP), DoCoMo i-mode, XHTML Basic or other adaptations of HTML and XML, have proved more popular. The PyGopherd server, however, provides a built-in WML front-end to Gopher sites served with it.

Gopher support in Web browsers

File:Firefox Gopher Directory Listing.png

Mozilla Firefox 3.7 displaying the top-level menu of the Floodgap gopher server

Browser	Currently Supported	Supported from	Supported until	Notes
Internet Explorer	No	1	6.0 RTM	Re-enable with registry patch. Always uses port 70.
Template:Rh2 | Internet Explorer for Mac	No		5.0	PowerPC-only
Mozilla Firefox	Yes	0		Always uses port 70. (May however be dropped from Firefox from version 4.0 onwards due to security concerns.)
SeaMonkey	Yes	1.0
Camino	Yes	1.0
OmniWeb	Yes	5.9.2	Current	First WebKit Browser to support Gopher
Epiphany	Yes
Galeon	Yes
Konqueror	Plugin			kio_gopher
K-Meleon	Yes
Lynx	Yes			Complete support
ELinks	Beta			Build option
Safari	No
Opera	No			Opera 9.0 includes a proxy capability
Google Chrome	No

Gopher support was disabled in Internet Explorer versions 5.* and 6 for Windows in June 2002 by a patch meant to fix a security vulnerability in the browser's Gopher protocol handler; however, it can be re-enabled by editing the Windows registry. In Internet Explorer 7, Gopher support was removed on the WinINET level.

Other browsers, including Mozilla Application Suite (deprecated), still support the protocol, but incompletely—the most obvious deficiency is that they cannot display the informational text found on many Gopher menus.

Gopher clients

Gopher was at its height of popularity during a time when there were still many equally competing computer architectures and operating systems. As such, there are several Gopher Clients available for Acorn RISC OS, AmigaOS, Atari MiNT, CMS, DOS, MacOS 7x, MVS, NeXT, OS/2 Warp, most UNIX-like operating systems, VMS, Windows 3x, and Windows 9x. GopherVR was a client designed for 3D visualization, and there is even a Gopher Client MOO object. The majority of these clients are hard coded to work on Port 70.

A copy of every known Gopher Client is permanently archived on the HAL3000 Gopher Server. The Clients may be freely downloaded from the HTTP link: http://hal3000.cx:70/Begin_Here/Clients

Gopher to HTTP gateways

Users of Web browsers that have incomplete or no support for Gopher can access content on Gopher servers via a server gateway that converts Gopher menus into HTML. GN and PyGopherd are two examples of Gopher server software that have built-in Gopher to HTTP interfaces. An active example of such a dual protocol server is Hal3000. Another is Floodgap. By default any Squid cache proxy server will act as a Gopher to HTTP gateway.

Gopher characteristics

Gopher functions and appears much like a mountable read-only global network file system (and software, such as gopherfs, is available that can actually mount a Gopher server as a FUSE resource). At a minimum, whatever a person can do with data files on a CD-ROM, they can do on Gopher.

A Gopher system consists of a series of hierarchical hyperlinkable menus. The choice of menu items and titles is controlled by the administrator of the server.

File:Floodgap gopher top menu.PNG

The top level menu of a Gopher server. Selecting the "Fun and Games" menu item...

File:Floodgap gopher fun menu.PNG

... takes the user to the "Fun and Games" menu.

File:Floodgap gopher servers menu.PNG

A Gopher menu listing other accessible servers.

File:Umn gopher dir.png

Gopher menu from a terminal client.

Similar to a file on a Web server, a file on a Gopher server can be linked to as a menu item from any other Gopher server. Many servers take advantage of this inter-server linking to provide a directory of other servers that the user can access.

Technical details

Protocol

The Gopher protocol was first described in INFORMATIONAL RFC 1436. IANA has assigned TCP port 70 to the Gopher protocol.

The gopher protocol is extremely simple in its conception, making it possible to browse without using a client. A standard gopher Telnet session may therefore appear as follows:

telnet quux.org 70
Trying 64.85.160.193...
Connected to quux.org.
Escape character is '^]'.
/Reference
1CIA World Factbook     /Archives/mirrors/textfiles.com/politics/CIA    gopher.quux.org 70
0Jargon 4.2.0   /Reference/Jargon 4.2.0 gopher.quux.org 70      +
1Online Libraries       /Reference/Online Libraries     gopher.quux.org 70     +
1RFCs: Internet Standards       /Computers/Standards and Specs/RFC      gopher.quux.org 70
1U.S. Gazetteer /Reference/U.S. Gazetteer       gopher.quux.org 70      +
iThis file contains information on United States        fake    (NULL)  0
icities, counties, and geographical areas.  It has      fake    (NULL)  0
ilatitude/longitude, population, land and water area,   fake    (NULL)  0
iand ZIP codes. fake    (NULL)  0
i       fake    (NULL)  0
iTo search for a city, enter the city's name.  To search        fake    (NULL) 0
ifor a county, use the name plus County -- for instance,        fake    (NULL) 0
iDallas County. fake    (NULL)  0
Connection closed by foreign host.

Here, the client has established a TCP connection with the server, on Port 70, the standard gopher port. The client then sends "/Reference" followed by a carriage return followed by a line feed (a "CR + LF" sequence). This is the item selector, which identifies the document to be retrieved. If the item selector were an empty line, the default directory will be selected. The server then replies with the requested item and closes the connection. According to the protocol, before the connection is closed, the server should send a full-stop on a line by itself. However, as is the case here, not all servers conform to this part of the protocol and the server may close the connection without returning the final full-stop.

In this example, the item sent back is a directory, consisting of a sequence of lines, each of which describes an item that can be retrieved. Most clients will display these as hypertext links, and so allow the user to navigate through the gopherspace by following the links.

All lines in a directory listing are ended with "CR + LF" and consist of five fields: Type (see below), User_Name (i.e. the description text to display), Selector (i.e. a file-system pathname), Host (i.e. the domain name of the server on which the item resides), and Port (i.e. the port number used by that server). The Type and User_Name fields are joined without a space; while the other fields are separated by tabs.

Because of the simplicity of the Gopher protocol, in the Windows or UNIX command-line (if you have netcat), you can easily download files from gopher using a command like the following:

echo jacks/jack.exe | nc gopher.example.org 70 > jack.exe

Gopher File-Types

File-types are described in gopher menus by a single number or (case specific) letter. Every client must understand file-types 0 and 1. All known clients understand file-types 0 through 9, g, and s; while all but the very oldest also understand file-types h and i.

• 0 = plain text file
• 1 = directory menu listing
• 2 = CSO search query
• 3 = error message
• 4 = BinHex encoded text file
• 5 = binary archive file
• 6 = UUEncoded text file
• 7 = search engine query
• 8 = telnet session pointer
• 9 = binary file
• g = GIF image file
• h = HTML file
• i = informational message
• I = Image file of unspecified format. Client decides how to display.
• s = Audio file format, primarily a WAV file
• T = tn3270 session pointer

A list of additional file-type definitions has continued to evolve over time, with some clients supporting them and others not. As such, many servers assign the generic 9 to every binary file, hoping that the client's computer will be able to correctly process the file.

URL links

Historically, to create a link to a Web server, "GET /" was used as the file to simulate an HTTP client request. John Goerzen created an addition to the Gopher protocol, commonly referred to as "URL links", that allows links to any protocol that supports URLs. For example, to create a link to http://gopher.quux.org, the item type is "h", the description is arbitrary, the item selector is "URL:http://gopher.quux.org", and the domain and port are that of the originating Gopher server. For clients that do not support URL links, the server creates an HTML redirection page.

Related technology

The master Gopherspace search engine is Veronica. Veronica offers a keyword search of all the public Internet Gopher server menu titles. A Veronica search produces a menu of Gopher items, each of which is a direct pointer to a Gopher data source.

Example of the Veronica Search Engine:

gopher://hal3000.cx/1/Search%09%09%2B

Individual Gopher servers often use a localized Search Engine called Jughead (renamed Jugtail).

---

GopherVR is a 3D virtual reality variant of the original Gopher system.

Gopher server software

A copy of every known Gopher Server is permanently archived on the HAL3000 Gopher Server. The Servers may be freely downloaded from the HTTP link http://hal3000.cx:70/Begin_Here/Servers

• Aftershock — written in Java.
• Bucktooth — modern gopher server written in Perl.
• Geomyidae — written in C. Public domain
• GN
• GoFish
• GOPHSERV — cross-platform, GPLv3, FreeBASIC.
• Gopher Cannon — Win32/Win64, freeware, written in .NET 3.5
• Goscher — written in Scheme.
• Grumpy — Linux, GPLv3, written in FreeBASIC.
• mgod
• PyGopherd — modern gopher+ server written in Python.
• PyGS

See also

• Veronica — the search engine system for the Gopher protocol, an acronym for "Very Easy Rodent-Oriented Net-wide Index to Computer Archives".
• Jugtail — an alternative search engine system for the Gopher protocol. Jugtail was formerly known as Jughead.
• Gopher+ — early proposed extensions to the Gopher protocol
• Super Dimension Fortress — a non-profit organization which provides free Gopher hosting
• Phlog — The gopher version of a weblog
• Wide area information server — a search engine whose popularity was contemporary with Gopher

External links

• "Start Page" for persons new to the Gopher protocol
• List of all public Gopher servers
• List of public Gopher server uptimes (gopher link)
• Known Gopher servers uptime and current state
• An announcement of Gopher on the Usenet Oct 8 1991
• Spencer Hunter's Homepage — Example of a Gopher emulation in HTML, online since 1995. Under the "About this gopher and myself" directory is the author's own Gopher manifesto, "Why gopher is superior to the Web."
• A community server for the Collier County, FL (Naples, FL) area whose fast web interface is inspired by Gopher. It is also an example of a Gopher emulation in HTML
• An article published by the technology discussion site "Ars Technica", about the Gopher community of enthusiasts nowadays

Standards

• Permanent Gopher Reference Material Repository
• IANA Port Number allocations
• RFC 1436 — The Internet Gopher Protocol (a distributed document search and retrieval protocol)
• RFC 1580 — Guide to Network Resource Tools
• RFC 1689 — Networked Information Retrieval: Tools and Groups
• RFC 1738 — Uniform Resource Locators (URL)
• RFC 1808 — Relative Uniform Resource Locators
• RFC 2396 — Uniform Resource Identifiers (URI): Generic Syntax
• RFC 4266 — The gopher URI Scheme