The gopher URI Scheme (RFC4266)
Original Publication Date: 2005-Nov-01
Included in the Prior Art Database: 2005-Nov-19
Internet Society Requests For Comment (RFCs)
This document specifies the gopher Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.
Network Working Group P.
Request for Comments: 4266 VPN Consortium
Obsoletes: 1738 November 2005
Category: Standards Track
The gopher URI Scheme
Status of This Memo
specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2005).
This document specifies
the gopher Uniform Resource Identifier (URI)
scheme that was originally specified in RFC 1738. The purpose of
this document is to allow RFC 1738 to be made obsolete while keeping
the information about the scheme on standards track.
previously defined in RFC 2396 [RFC2396], which was updated
by RFC 3986 [RFC3986]. Those documents also specify how to define
schemes for URIs.
definition for many URI schemes appeared in RFC 1738
[RFC1738]. Because that document has been made obsolete, this
document copies the gopher URI scheme from it to allow that material
to remain on standards track.
2. Scheme Definition
The gopher URL
scheme is used to designate Internet resources
accessible using the Gopher protocol.
The base Gopher
protocol is described in RFC 1436 [RFC1436] and
supports items and collections of items (directories). The Gopher+
protocol is a set of upward-compatible extensions to the base Gopher
protocol and is described in [Gopher+]. Gopher+ supports associating
Hoffman Standards Track [Page 1]
RFC 4266 The gopher URI Scheme November 2005
arbitrary sets of attributes and alternate data representations with
Gopher items. Gopher URLs accommodate both Gopher and Gopher+ items
and item attributes.
The Gopher protocol was widely implemented in the
early 1990s, but few Gopher servers are in use today.
2.1. Gopher URL Syntax
A Gopher URL takes the form:
where <gopher-path> is one of:
is omitted, the port defaults to 70. <gophertype> is a
single-character field to denote the Gopher type of the resource to
which the URL...