RFC 2295: Transparent Content Negotiation in HTTP
In plain English — editorial summary, not part of the RFC
HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
Document record
- Document ID
- RFC2295
- Published
- March 1998
- Authors
- K. Holtman; A. Mutz
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 58
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4248The telnet URI SchemeCurrent
October 2005
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2244ACAP -- Application Configuration Access ProtocolUpdated
November 1997
- RFC 2227Simple Hit-Metering and Usage-Limiting for HTTPCurrent
October 1997
- RFC 2392Content-ID and Message-ID Uniform Resource LocatorsCurrent
August 1998
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
- RFC 2616Hypertext Transfer Protocol -- HTTP/1.1Obsoleted
June 1999
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?