RFC 1866: Hypertext Markup Language - 2.0
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2854.
Current document in this lineage: RFC 2854 — The 'text/html' Media Type
In plain English — editorial summary, not part of the RFC
This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK]
Document record
- Document ID
- RFC1866
- Published
- November 1995
- Authors
- T. Berners-Lee; D. Connolly
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 77
- Also known as
- —
- Obsoleted by:
- RFC 2854
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1942HTML TablesObsoleted
May 1996
- RFC 2070Internationalization of the Hypertext Markup LanguageObsoleted
January 1997
- RFC 2594Definitions of Managed Objects for WWW ServicesCurrent
May 1999
- RFC 2616Hypertext Transfer Protocol -- HTTP/1.1Obsoleted
June 1999
- RFC 2660The Secure HyperText Transfer ProtocolCurrent
August 1999
- RFC 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
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?