RFC 1808: Relative Uniform Resource Locators
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3986.
Current document in this lineage: RFC 3986 — Uniform Resource Identifier (URI): Generic Syntax
In plain English — editorial summary, not part of the RFC
In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1808
- Published
- June 1995
- Authors
- R. Fielding
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 16
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1808 (1995)
- RFC 2396 (1998)
- RFC 2732 (1999)
- RFC 3986 (2005) ✓
Read the full history of Uniform Resource Identifier (URI): Generic Syntax →
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2717Registration Procedures for URL Scheme NamesObsoleted
November 1999
- RFC 2718Guidelines for new URL SchemesObsoleted
November 1999
- RFC 3731Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
March 2004
- RFC 3732Extensible Provisioning Protocol (EPP) Host MappingObsoleted
March 2004
- RFC 3733Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
March 2004
- RFC 4395Guidelines and Registration Procedures for New URI SchemesObsoleted
February 2006
- RFC 4931Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
May 2007
- RFC 4932Extensible Provisioning Protocol (EPP) Host MappingObsoleted
May 2007
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?