RFC 1738: Uniform Resource Locators (URL)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4248, RFC 4266.
Current document in this lineage: RFC 4248 — The telnet URI Scheme; RFC 4266 — The gopher URI Scheme
In plain English — editorial summary, not part of the RFC
This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1738
- Published
- December 1994
- Authors
- T. Berners-Lee; L. Masinter; M. McCahill
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1738 (1994)
- RFC 4248 (2005)
- RFC 4266 (2005) ✓
Referenced by
9 later RFCs formally update or obsolete part of this document.
- RFC 1808Relative Uniform Resource LocatorsObsoleted
June 1995
- RFC 2368The mailto URL schemeObsoleted
July 1998
- RFC 2396Uniform Resource Identifiers (URI): Generic SyntaxObsoleted
August 1998
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 4248The telnet URI SchemeCurrent
October 2005
- RFC 4266The gopher URI SchemeCurrent
November 2005
- RFC 6196Moving mailserver: URI Scheme to HistoricCurrent
March 2011
- RFC 6270The 'tn3270' URI SchemeCurrent
June 2011
- RFC 8089The "file" URI SchemeUpdated
February 2017
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1736Functional Recommendations for Internet Resource LocatorsCurrent
February 1995
- RFC 2056Uniform Resource Locators for Z39.50Current
November 1996
- RFC 2187Application of Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 2345Domain Names and Company Name RetrievalCurrent
May 1998
- RFC 2369The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header FieldsCurrent
July 1998
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 2244ACAP -- Application Configuration Access ProtocolUpdated
November 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?