draft-ietf-httpbis-safe-method-w-body-09.txt		draft-ietf-httpbis-safe-method-w-body-latest.txt
	HTTP Working Group J. Reschke		HTTP Working Group J. Reschke
	Internet-Draft greenbytes		Internet-Draft greenbytes
	Intended status: Standards Track J.M. Snell		Intended status: Standards Track J.M. Snell
	Expires: October 7, 2025		Expires: October 12, 2025
	M. Bishop		M. Bishop
	Akamai		Akamai
	April 5, 2025		April 10, 2025
	The HTTP QUERY Method		The HTTP QUERY Method
	draft-ietf-httpbis-safe-method-w-body-09		draft-ietf-httpbis-safe-method-w-body-latest
	Abstract		Abstract
	This specification defines a new HTTP method, QUERY, as a safe,		This specification defines a new HTTP method, QUERY, as a safe,
	idempotent request method that can carry request content.		idempotent request method that can carry request content.
	Editorial Note		Editorial Note
	This note is to be removed before publishing as an RFC.		This note is to be removed before publishing as an RFC.
	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
	<https://lists.w3.org/Archives/Public/ietf-http-wg/>.		<https://lists.w3.org/Archives/Public/ietf-http-wg/>.
	Working Group information can be found at <https://httpwg.org/>;		Working Group information can be found at <https://httpwg.org/>;
	source code and issues list for this draft can be found at		source code and issues list for this draft can be found at
	<https://github.com/httpwg/http-extensions/labels/query-method>.		<https://github.com/httpwg/http-extensions/labels/query-method>.
	The changes in this draft are summarized in Appendix B.9.		The changes in this draft are summarized in Appendix B.10.
	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 October 7, 2025.		This Internet-Draft will expire on October 12, 2025.
	Copyright Notice		Copyright Notice
	Copyright (c) 2025 IETF Trust and the persons identified as the		Copyright (c) 2025 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 3, line 8 ¶		skipping to change at page 3, line 8 ¶
	Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 18		Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 18
	B.1. Since draft-ietf-httpbis-safe-method-w-body-00 . . . . . 18		B.1. Since draft-ietf-httpbis-safe-method-w-body-00 . . . . . 18
	B.2. Since draft-ietf-httpbis-safe-method-w-body-01 . . . . . 19		B.2. Since draft-ietf-httpbis-safe-method-w-body-01 . . . . . 19
	B.3. Since draft-ietf-httpbis-safe-method-w-body-02 . . . . . 19		B.3. Since draft-ietf-httpbis-safe-method-w-body-02 . . . . . 19
	B.4. Since draft-ietf-httpbis-safe-method-w-body-03 . . . . . 19		B.4. Since draft-ietf-httpbis-safe-method-w-body-03 . . . . . 19
	B.5. Since draft-ietf-httpbis-safe-method-w-body-04 . . . . . 19		B.5. Since draft-ietf-httpbis-safe-method-w-body-04 . . . . . 19
	B.6. Since draft-ietf-httpbis-safe-method-w-body-05 . . . . . 19		B.6. Since draft-ietf-httpbis-safe-method-w-body-05 . . . . . 19
	B.7. Since draft-ietf-httpbis-safe-method-w-body-06 . . . . . 20		B.7. Since draft-ietf-httpbis-safe-method-w-body-06 . . . . . 20
	B.8. Since draft-ietf-httpbis-safe-method-w-body-07 . . . . . 21		B.8. Since draft-ietf-httpbis-safe-method-w-body-07 . . . . . 21
	B.9. Since draft-ietf-httpbis-safe-method-w-body-08 . . . . . 21		B.9. Since draft-ietf-httpbis-safe-method-w-body-08 . . . . . 21
			B.10. Since draft-ietf-httpbis-safe-method-w-body-09 . . . . . 21
	Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 21		Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 21
	Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 21		Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
	1. Introduction		1. Introduction
	This specification defines the HTTP QUERY request method as a means		This specification defines the HTTP QUERY request method as a means
	of making a safe, idempotent request that contains content.		of making a safe, idempotent request that contains content.
	Most often, this is desirable when the data conveyed in a request is		Most often, this is desirable when the data conveyed in a request is
	too voluminous to be encoded into the request's URI. For example,		too voluminous to be encoded into the request's URI. For example,
	this is a common query pattern:		this is a common query pattern:
	skipping to change at page 21, line 28 ¶		skipping to change at page 21, line 28 ¶
	o Avoid term 'query parameters' (<https://github.com/httpwg/http-		o Avoid term 'query parameters' (<https://github.com/httpwg/http-
	extensions/issues/3019>)		extensions/issues/3019>)
	o Add missing references, fixed terminology		o Add missing references, fixed terminology
	(<https://github.com/httpwg/http-extensions/issues/3021>)		(<https://github.com/httpwg/http-extensions/issues/3021>)
	o Add Acknowledgements/Contributors sections; moved Ashok to		o Add Acknowledgements/Contributors sections; moved Ashok to
	Contributors (<https://github.com/httpwg/http-extensions/		Contributors (<https://github.com/httpwg/http-extensions/
	issues/3029>)		issues/3029>)
	o Hopefully more clarity wrt query content vs URI query conponent		o Hopefully more clarity wrt query content vs URI query component
	(<https://github.com/httpwg/http-extensions/issues/3059>)		(<https://github.com/httpwg/http-extensions/issues/3059>)
			B.10. Since draft-ietf-httpbis-safe-method-w-body-09
			None yet.
	Acknowledgements		Acknowledgements
	We thank all members of the HTTP Working Group for ideas, reviews,		We thank all members of the HTTP Working Group for ideas, reviews,
	and feedback.		and feedback.
	The following individuals deserve special recognition: Carsten		The following individuals deserve special recognition: Carsten
	Bormann, Mark Nottingham, Martin Thomson, Michael Thornburgh, Roberto		Bormann, Mark Nottingham, Martin Thomson, Michael Thornburgh, Roberto
	Polli, Roy Fielding, and Will Hawkins.		Polli, Roy Fielding, and Will Hawkins.
	Contributors		Contributors
End of changes. 9 change blocks.
	7 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/