draft-ietf-httpbis-safe-method-w-body-01.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
	Updates: 5323 (if approved) A. Malhotra		Updates: 5323 (if approved) A. Malhotra
	Intended status: Standards Track		Intended status: Standards Track
	Expires: December 10, 2021 J.M. Snell		Expires: January 2, 2022 J.M. Snell
	June 8, 2021		July 1, 2021
	HTTP SEARCH Method		HTTP SEARCH Method
	draft-ietf-httpbis-safe-method-w-body-01		draft-ietf-httpbis-safe-method-w-body-latest
	Abstract		Abstract
	This specification updates the definition and semantics of the HTTP		This specification updates the definition and semantics of the HTTP
	SEARCH request method originally defined by RFC 5323.		SEARCH request method originally defined by RFC 5323.
	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/safe-method-		<https://github.com/httpwg/http-extensions/labels/safe-method-
	w-body>.		w-body>.
	The changes in this draft are summarized in Appendix A.1.		The changes in this draft are summarized in Appendix A.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 December 10, 2021.		This Internet-Draft will expire on January 2, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 2, line 32 ¶		skipping to change at page 2, line 32 ¶
	2. SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. The "Accept-Search" Header Field . . . . . . . . . . . . . . 5		3. The "Accept-Search" Header Field . . . . . . . . . . . . . . 5
	4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6		4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4.1. Simple SEARCH with a Direct Response . . . . . . . . . . 6		4.1. Simple SEARCH with a Direct Response . . . . . . . . . . 6
	4.2. Simple SEARCH with indirect response (303 See Other) . . 6		4.2. Simple SEARCH with indirect response (303 See Other) . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 7		5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	7. Normative References . . . . . . . . . . . . . . . . . . . . 7		7. Normative References . . . . . . . . . . . . . . . . . . . . 7
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
	A.1. Since draft-ietf-httpbis-safe-method-w-body-00 . . . . . 8		A.1. Since draft-ietf-httpbis-safe-method-w-body-00 . . . . . 8
			A.2. Since draft-ietf-httpbis-safe-method-w-body-01 . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	This specification updates the HTTP SEARCH method originally defined		This specification updates the HTTP SEARCH method originally defined
	in [RFC5323].		in [RFC5323].
	Many existing HTTP-based applications use the HTTP GET and POST		Many existing HTTP-based applications use the HTTP GET and POST
	methods in various ways to implement the functionality provided by		methods in various ways to implement the functionality provided by
	SEARCH.		SEARCH.
	skipping to change at page 5, line 15 ¶		skipping to change at page 5, line 15 ¶
	SEARCH requests are both safe and idempotent with regards to the		SEARCH requests are both safe and idempotent with regards to the
	resource identified by the request URI. That is, SEARCH requests do		resource identified by the request URI. That is, SEARCH requests do
	not alter the state of the targeted resource. However, while		not alter the state of the targeted resource. However, while
	processing a search request, a server can be expected to allocate		processing a search request, a server can be expected to allocate
	computing and memory resources or even create additional HTTP		computing and memory resources or even create additional HTTP
	resources through which the response can be retrieved.		resources through which the response can be retrieved.
	A successful response to a SEARCH request is expected to provide some		A successful response to a SEARCH request is expected to provide some
	indication as to the final disposition of the search operation. For		indication as to the final disposition of the search operation. For
	instance, a successful search that yields no results can be		instance, a successful search that yields no results can be
	represented by a 204 No Content response. If the response includes a		represented by a 204 No Content response. If the response includes
	content, it is expected to describe the results of the search		content, it is expected to describe the results of the search
	operation. In some cases, the server may choose to respond		operation. In some cases, the server may choose to respond
	indirectly to the SEARCH request by returning a 3xx Redirection with		indirectly to the SEARCH request by returning a 3xx Redirection with
	a Location header field specifying an alternate Request URI from		a Location header field specifying an alternate Request URI from
	which the search results can be retrieved using an HTTP GET request.		which the search results can be retrieved using an HTTP GET request.
	Various non-normative examples of successful SEARCH responses are		Various non-normative examples of successful SEARCH responses are
	illustrated in Section 4.		illustrated in Section 4.
	The response to a SEARCH request is not cacheable. It ought to be		The response to a SEARCH request is not cacheable. It ought to be
	noted, however, that because SEARCH requests are safe and idempotent,		noted, however, that because SEARCH requests are safe and idempotent,
	skipping to change at page 9, line 8 ¶		skipping to change at page 9, line 8 ¶
	o Reference RFC 8174 and markup bcp14 terms		o Reference RFC 8174 and markup bcp14 terms
	(<https://github.com/httpwg/http-extensions/issues/1497>)		(<https://github.com/httpwg/http-extensions/issues/1497>)
	o Update HTTP reference (<https://github.com/httpwg/http-extensions/		o Update HTTP reference (<https://github.com/httpwg/http-extensions/
	issues/1524>)		issues/1524>)
	o Relax restriction of generic XML media type in request body		o Relax restriction of generic XML media type in request body
	(<https://github.com/httpwg/http-extensions/issues/1535>)		(<https://github.com/httpwg/http-extensions/issues/1535>)
			A.2. Since draft-ietf-httpbis-safe-method-w-body-01
			None yet.
	Authors' Addresses		Authors' Addresses
	Julian Reschke		Julian Reschke
	greenbytes GmbH		greenbytes GmbH
	Hafenweg 16		Hafenweg 16
	48155 Münster		48155 Münster
	Germany		Germany
	Email: julian.reschke@greenbytes.de		Email: julian.reschke@greenbytes.de
	URI: https://greenbytes.de/tech/webdav/		URI: https://greenbytes.de/tech/webdav/
End of changes. 7 change blocks.
	6 lines changed or deleted		11 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/