draft-fielding-httpbis-http-conditional-00.txt		draft-fielding-httpbis-http-conditional-latest.txt
	Network Working Group R. Fielding, Ed.		Network Working Group R. Fielding, Ed.
	Internet-Draft Adobe		Internet-Draft Adobe
	Obsoletes: 7232 (if approved) J. Reschke, Ed.		Obsoletes: 7232 (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 (HTTP): Conditional Requests		Hypertext Transfer Protocol (HTTP): Conditional Requests
	draft-fielding-httpbis-http-conditional-00		draft-fielding-httpbis-http-conditional-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 HTTP/1.1 conditional requests,		systems. This document defines HTTP/1.1 conditional requests,
	including metadata header fields for indicating state changes,		including metadata header fields for indicating state changes,
	request header fields for making preconditions on such state, and		request header fields for making preconditions on such state, and
	rules for constructing the responses to a conditional request when		rules for constructing the responses to a conditional request when
	one or more preconditions evaluate to false.		one or more preconditions evaluate to false.
	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 7232 have been collected at <https://www.rfc-		Errata for RFC 7232 have been collected at <https://www.rfc-
	editor.org/errata_search.php?rfc=7232>, and an additional issues list		editor.org/errata_search.php?rfc=7232>, 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 D.1.		The changes in this draft are summarized in Appendix D.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 3, line 32 ¶		skipping to change at page 3, line 32 ¶
	7.2. Header Field Registration . . . . . . . . . . . . . . . . 21		7.2. Header Field Registration . . . . . . . . . . . . . . . . 21
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 21		8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
	9.1. Normative References . . . . . . . . . . . . . . . . . . 22		9.1. Normative References . . . . . . . . . . . . . . . . . . 22
	9.2. Informative References . . . . . . . . . . . . . . . . . 23		9.2. Informative References . . . . . . . . . . . . . . . . . 23
	Appendix A. Changes from RFC 7232 . . . . . . . . . . . . . . . 24		Appendix A. Changes from RFC 7232 . . . . . . . . . . . . . . . 24
	Appendix B. Imported ABNF . . . . . . . . . . . . . . . . . . . 24		Appendix B. Imported ABNF . . . . . . . . . . . . . . . . . . . 24
	Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 24		Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 24
	Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 25		Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 25
	D.1. Since RFC 7232 . . . . . . . . . . . . . . . . . . . . . 25		D.1. Since RFC 7232 . . . . . . . . . . . . . . . . . . . . . 25
			D.2. Since draft-fielding-httpbis-conditional-00 . . . . . . . 26
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 27		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 27
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
	1. Introduction		1. Introduction
	Conditional requests are HTTP requests [SEMNTCS] that include one or		Conditional requests are HTTP requests [SEMNTCS] that include one or
	more header fields indicating a precondition to be tested before		more header fields indicating a precondition to be tested before
	applying the method semantics to the target resource. This document		applying the method semantics to the target resource. This document
	defines the HTTP/1.1 conditional request mechanisms in terms of the		defines the HTTP/1.1 conditional request mechanisms in terms of the
	skipping to change at page 22, line 23 ¶		skipping to change at page 22, line 23 ¶
	to ensure that the cache is cleared or replaced whenever the user		to ensure that the cache is cleared or replaced whenever the user
	performs privacy-maintaining actions, such as clearing stored cookies		performs privacy-maintaining actions, such as clearing stored cookies
	or changing to a private browsing mode.		or changing to a private browsing mode.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[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.
	[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.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax		[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234,		Specifications: ABNF", STD 68, RFC 5234,
	DOI 10.17487/RFC5234, January 2008,		DOI 10.17487/RFC5234, January 2008,
	<https://www.rfc-editor.org/info/rfc5234>.		<https://www.rfc-editor.org/info/rfc5234>.
	[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Semantics and Content", draft-fielding-		Protocol (HTTP): Semantics and Content", draft-fielding-
	httpbis-http-semantics-00 (work in progress), March 2018.		httpbis-http-semantics-latest (work in progress), March
			2018.
	9.2. Informative References		9.2. Informative References
	[BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration		[BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration
	Procedures for Message Header Fields", BCP 90, RFC 3864,		Procedures for Message Header Fields", BCP 90, RFC 3864,
	September 2004, <https://www.rfc-editor.org/info/bcp90>.		September 2004, <https://www.rfc-editor.org/info/bcp90>.
	[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,		[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext		Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
	Transfer Protocol -- HTTP/1.1", RFC 2616,		Transfer Protocol -- HTTP/1.1", RFC 2616,
	skipping to change at page 26, line 5 ¶		skipping to change at page 26, 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.
			D.2. Since draft-fielding-httpbis-conditional-00
			None yet.
	Index		Index
	3		3
	304 Not Modified (status code) 17		304 Not Modified (status code) 17
	4		4
	412 Precondition Failed (status code) 18		412 Precondition Failed (status code) 18
	E		E
	ETag header field 8		ETag header field 8
End of changes. 10 change blocks.
	10 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/