Technology and engineering · 2019
RFC 8674: The "safe" HTTP Preference
by M. Nottingham
This specification defines a preference for HTTP requests that expresses a desire to avoid objectionable content, according to the definition of that term by the origin server. This specification does not define a precise semantic for "safe". Rather, the term is interpreted by the server and within the scope of each web site that chooses to act upon this information. Support for this preference by clients and servers is optional.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2019
- Status
- Informational
- Pages
- 7
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.