RFC 2296: HTTP Remote Variant Selection Algorithm -- RVSA/1.0
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 a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0.
Document record
- Document ID
- RFC2296
- Published
- March 1998
- Authors
- K. Holtman; A. Mutz
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2310The Safe Response Header FieldCurrent
April 1998
- RFC 2276Architectural Principles of Uniform Resource Name ResolutionUpdated
January 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 2017Definition of the URL MIME External-Body Access-TypeCurrent
October 1996
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
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?