RFC 2310: The Safe Response Header Field
In plain English — editorial summary, not part of the RFC
This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. Such an indication will allow user agents to handle retries of some safe requests, in particular safe POST requests, in a more user-friendly way.
Document record
- Document ID
- RFC2310
- Published
- April 1998
- Authors
- K. Holtman
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2186Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 2112The MIME Multipart/Related Content-typeObsoleted
March 1997
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 2110MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)Obsoleted
March 1997
- RFC 2109HTTP State Management MechanismObsoleted
February 1997
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 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?