Skip to content

Commit 4cd3be3

Browse files
authored
QUERY: Explain relation to SEARCH etc (closes #3337) (#3338)
1 parent 5d195f1 commit 4cd3be3

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

draft-ietf-httpbis-safe-method-w-body.xml

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -683,6 +683,9 @@ Accept-Query: "application/jsonpath", application/sql;charset="UTF-8"</artwork>
683683
<author><organization>WHATWG</organization></author>
684684
</front>
685685
</reference>
686+
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.3253.xml"/>
687+
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.4918.xml"/>
688+
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.5323.xml"/>
686689
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.6838.xml"/>
687690
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8259.xml"/>
688691
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.9535.xml"/>
@@ -1355,6 +1358,29 @@ Last-Modified: Thu, 20 Feb 2025 06:10:01 GMT
13551358
</section>
13561359
</section>
13571360

1361+
<section title="Selection of the Method Name 'QUERY'" anchor="selection.method.name">
1362+
<t>
1363+
The HTTP Method Registry (<eref target="http://www.iana.org/assignments/http-methods"/>)
1364+
already contains three other methods with the properties "safe" and "idempotent":
1365+
"PROPFIND" (<xref target="RFC4918"/>), REPORT" (<xref target="RFC3253"/>), and
1366+
"SEARCH" (<xref target="RFC5323"/>).
1367+
</t>
1368+
<t>
1369+
It would have been possible to re-use any of these, updating it in a way that it matches
1370+
what this specification defines as the new method "QUERY". Indeed, the early stages
1371+
of this specification used "SEARCH".
1372+
</t>
1373+
<t>
1374+
The method name "QUERY" ultimately was chosen because:
1375+
</t>
1376+
<ul>
1377+
<li>The alternatives use a generic media type for the request content ("application/xml"); the
1378+
semantics of the request depends solely on the request content.</li>
1379+
<li>Furthermore, they all originate from the WebDAV activity, about which many have mixed feelings.</li>
1380+
<li>"QUERY" captures the relation with the URI's query component well.</li>
1381+
</ul>
1382+
</section>
1383+
13581384
<section title="Change Log" anchor="change.log" removeInRFC="true">
13591385
<section title="Since draft-ietf-httpbis-safe-method-w-body-00" anchor="changes.since.00">
13601386
<ul>
@@ -1473,6 +1499,7 @@ Last-Modified: Thu, 20 Feb 2025 06:10:01 GMT
14731499
<li>URI reference is normative (<eref target="https://github.com/httpwg/http-extensions/issues/3331"/>)</li>
14741500
<li>inconsistency between Sections 2.4 and 4 wrt URI assignments (<eref target="https://github.com/httpwg/http-extensions/issues/3332"/>)</li>
14751501
<li>IESG review nits (<eref target="https://github.com/httpwg/http-extensions/issues/3333"/>)</li>
1502+
<li>Explain relation to SEARCH etc (<eref target="https://github.com/httpwg/http-extensions/issues/3337"/>)</li>
14761503
</ul>
14771504
</section>
14781505
</section>

0 commit comments

Comments
 (0)