draft-fielding-httpbis-http-semantics-00.txt   draft-fielding-httpbis-http-semantics-latest.txt 
Network Working Group R. Fielding, Ed. Network Working Group R. Fielding, Ed.
Internet-Draft Adobe Internet-Draft Adobe
Obsoletes: 7231 (if approved) J. Reschke, Ed. Obsoletes: 7231 (if approved) J. Reschke, Ed.
Intended status: Standards Track greenbytes Intended status: Standards Track greenbytes
Expires: September 6, 2018 March 5, 2018 Expires: September 18, 2018 March 17, 2018
Hypertext Transfer Protocol: Semantics and Content Hypertext Transfer Protocol: Semantics and Content
draft-fielding-httpbis-http-semantics-00 draft-fielding-httpbis-http-semantics-latest
Abstract Abstract
The Hypertext Transfer Protocol (HTTP) is a stateless application- The Hypertext Transfer Protocol (HTTP) is a stateless application-
level protocol for distributed, collaborative, hypertext information level protocol for distributed, collaborative, hypertext information
systems. This document defines the semantics of HTTP/1.1 messages, systems. This document defines the semantics of HTTP/1.1 messages,
as expressed by request methods, request header fields, response as expressed by request methods, request header fields, response
status codes, and response header fields, along with the payload of status codes, and response header fields, along with the payload of
messages (metadata and body content) and mechanisms for content messages (metadata and body content) and mechanisms for content
negotiation. negotiation.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
item of the HTTP Working Group._ item of the HTTP Working Group._
Discussion of this draft takes place on the HTTP working group Discussion of this draft takes place on the HTTP working group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
<http://lists.w3.org/Archives/Public/ietf-http-wg/>. <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
Errata for RFC 7231 have been collected at <https://www.rfc- Errata for RFC 7231 have been collected at <https://www.rfc-
editor.org/errata_search.php?rfc=7231>, and an additional issues list editor.org/errata_search.php?rfc=7231>, and an additional issues list
lives at <https://github.com/httpwg/http11bis/issues>. lives at <https://github.com/httpwg/http11bis/issues>.
The changes in this draft are summarized in Appendix E.1. The changes in this draft are summarized in Appendix E.2.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 6, 2018. This Internet-Draft will expire on September 18, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 38 skipping to change at page 5, line 38
A.2. Conversion to Canonical Form . . . . . . . . . . . . . . 90 A.2. Conversion to Canonical Form . . . . . . . . . . . . . . 90
A.3. Conversion of Date Formats . . . . . . . . . . . . . . . 91 A.3. Conversion of Date Formats . . . . . . . . . . . . . . . 91
A.4. Conversion of Content-Encoding . . . . . . . . . . . . . 91 A.4. Conversion of Content-Encoding . . . . . . . . . . . . . 91
A.5. Conversion of Content-Transfer-Encoding . . . . . . . . . 91 A.5. Conversion of Content-Transfer-Encoding . . . . . . . . . 91
A.6. MHTML and Line Length Limitations . . . . . . . . . . . . 91 A.6. MHTML and Line Length Limitations . . . . . . . . . . . . 91
Appendix B. Changes from RFC 7231 . . . . . . . . . . . . . . . 92 Appendix B. Changes from RFC 7231 . . . . . . . . . . . . . . . 92
Appendix C. Imported ABNF . . . . . . . . . . . . . . . . . . . 92 Appendix C. Imported ABNF . . . . . . . . . . . . . . . . . . . 92
Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 92 Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 92
Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 95 Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 95
E.1. Since RFC 7231 . . . . . . . . . . . . . . . . . . . . . 95 E.1. Since RFC 7231 . . . . . . . . . . . . . . . . . . . . . 95
E.2. Since draft-fielding-httpbis-semantics-00 . . . . . . . . 96
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 100 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 100
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 100
1. Introduction 1. Introduction
Each Hypertext Transfer Protocol (HTTP) message is either a request Each Hypertext Transfer Protocol (HTTP) message is either a request
or a response. A server listens on a connection for a request, or a response. A server listens on a connection for a request,
parses each message received, interprets the message semantics in parses each message received, interprets the message semantics in
relation to the identified request target, and responds to that relation to the identified request target, and responds to that
skipping to change at page 85, line 39 skipping to change at page 85, line 39
the loss of privacy that might result if too much detail is provided. the loss of privacy that might result if too much detail is provided.
As an extreme privacy measure, proxies could filter the proactive As an extreme privacy measure, proxies could filter the proactive
negotiation header fields in relayed requests. negotiation header fields in relayed requests.
10. References 10. References
10.1. Normative References 10.1. Normative References
[AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP): Authentication", draft-fielding-httpbis- Protocol (HTTP): Authentication", draft-fielding-httpbis-
http-auth-00 (work in progress), March 2018. http-auth-latest (work in progress), March 2018.
[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, [CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft- Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft-
fielding-httpbis-http-cache-00 (work in progress), March fielding-httpbis-http-cache-latest (work in progress),
2018. March 2018.
[CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP): Conditional Requests", draft-fielding- Protocol (HTTP): Conditional Requests", draft-fielding-
httpbis-http-conditional-00 (work in progress), March httpbis-http-conditional-latest (work in progress), March
2018. 2018.
[MESSGNG] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [MESSGNG] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", draft- Protocol (HTTP/1.1): Message Syntax and Routing", draft-
fielding-httpbis-http-messaging-00 (work in progress), fielding-httpbis-http-messaging-latest (work in progress),
March 2018. March 2018.
[RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., [RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
"Hypertext Transfer Protocol (HTTP): Range Requests", "Hypertext Transfer Protocol (HTTP): Range Requests",
draft-fielding-httpbis-http-range-00 (work in progress), draft-fielding-httpbis-http-range-latest (work in
March 2018. progress), March 2018.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996,
<https://www.rfc-editor.org/info/rfc2045>. <https://www.rfc-editor.org/info/rfc2045>.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
DOI 10.17487/RFC2046, November 1996, DOI 10.17487/RFC2046, November 1996,
<https://www.rfc-editor.org/info/rfc2046>. <https://www.rfc-editor.org/info/rfc2046>.
skipping to change at page 96, line 5 skipping to change at page 96, line 5
o Update links to sibling specifications. o Update links to sibling specifications.
o Replace sections listing changes from RFC 2616 by new empty o Replace sections listing changes from RFC 2616 by new empty
sections referring to RFC 723x. sections referring to RFC 723x.
o Remove acknowledgements specific to RFC 723x. o Remove acknowledgements specific to RFC 723x.
o Move "Acknowledgements" to the very end and make them unnumbered. o Move "Acknowledgements" to the very end and make them unnumbered.
E.2. Since draft-fielding-httpbis-semantics-00
None yet.
Index Index
1 1
100 Continue (status code) 50 100 Continue (status code) 50
100-continue (expect value) 34 100-continue (expect value) 34
101 Switching Protocols (status code) 50 101 Switching Protocols (status code) 50
1xx Informational (status code class) 50 1xx Informational (status code class) 50
2 2
200 OK (status code) 51 200 OK (status code) 51
 End of changes. 11 change blocks. 
11 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/