RFC 3282: Content Language Headers
In plain English — editorial summary, not part of the RFC
This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3282
- Published
- May 2002
- Authors
- H. Alvestrand
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
- Obsoletes:
- RFC 1766
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
- RFC 3150End-to-end Performance Implications of Slow LinksCurrent
July 2001
- RFC 3545Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and ReorderingCurrent
July 2003
- RFC 2404The Use of HMAC-SHA-1-96 within ESP and AHCurrent
November 1998
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 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?