The Safe Response Header Field
RFC 2310
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['http', 'hyper', 'text', 'transfer', 'protocol']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "K. Holtman": changed name from "Koen Holtman" to "K. Holtman", changed affiliation from "TUE" to "Technische Universiteit Eindhoven", cleared country (was "5600 MB … Changed author "K. Holtman": changed name from "Koen Holtman" to "K. Holtman", changed affiliation from "TUE" to "Technische Universiteit Eindhoven", cleared country (was "5600 MB Eindhoven (The Netherlands)"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2021-12-10
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document defines a HTTP response header field called Safe, which can be used to indicate … Received changes through RFC Editor sync (changed abstract to '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.', changed standardization level to Historic) |
|
2021-12-06
|
Amy Vezza | New status of Historic approved by the IESG https://datatracker.ietf.org/doc/status-change-http-experiments-to-historic/ |
|
1998-04-01
|
(System) | RFC published |