Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Editorial changes to Safe Method With Body #2859

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Editorial changes to Safe Method With Body #2859

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4864476
Editorial changes to Safe Method With Body
hawkinsw Aug 7, 2024
3b10257
Update draft-ietf-httpbis-safe-method-w-body.xml
hawkinsw Sep 10, 2024
fd8d578
Update draft-ietf-httpbis-safe-method-w-body.xml
hawkinsw Sep 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 26 additions & 13 deletions draft-ietf-httpbis-safe-method-w-body.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,8 @@

<t>
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, while
this is an common and interoperable query:
too voluminous to be encoded into the request's URI. For example,
this is a common and interoperable query:
</t>

<artwork type="http-message">
Expand All @@ -109,18 +109,15 @@ Host: example.org
</artwork>

<t>
if the query parameters extend to several kilobytes or more of
data it may not be, because many implementations place limits on their size. Often these limits are not
known or discoverable ahead of time, because a request can pass through many uncoordinated
systems. Additionally, expressing some data in the target URI is inefficient, because it
needs to be encoded to be a valid URI.
</t>

<t>
Encoding query parameters directly into the request URI also effectively
casts every possible combination of query inputs as distinct
resources. Depending on the application, that may not be desirable.
However, for a query with parameters that extend to several kilobytes or more of
data, encoding it in the request URI may not be the best option because
hawkinsw marked this conversation as resolved.
Show resolved Hide resolved
</t>
<ul>
<li>many implementations place limitations on query size that are not discoverable ahead of time,</li>
<li>expressing some data in the target URI is inefficient because of the overhead of encoding that data into a valid URI, and</li>
<li>encoding query parameters directly into the request URI effectively casts every possible combination of query inputs as distinct
resources (for more information, see <xref target="NO-VARY-SEARCH"/>).</li>
hawkinsw marked this conversation as resolved.
Show resolved Hide resolved
</ul>

<t>
As an alternative to using GET, many implementations make use of the
Expand Down Expand Up @@ -410,6 +407,22 @@ Dubois, Camille, [email protected]
<seriesInfo name="RFC" value="9111"/>
</reference>
</references>
<references title="Informative References">
<reference anchor="NO-VARY-SEARCH"
target="https://datatracker.ietf.org/doc/html/draft-wicg-http-no-vary-search-01">
<front>
<title>No-Vary-Search</title>
<author initials="D." surname="Denicola" fullname="Domenic Denicola">
<organization>Google LLC</organization>
</author>
<author initials="J." surname="Roman" fullname="Jeremy Roman">
<organization>Google LLC</organization>
</author>
<date month="June" day="4" year="2024" />
</front>
<seriesInfo name="Internet-Draft" value="draft-wicg-http-no-vary-search-01" />
</reference>
</references>

<section title="Change Log" anchor="change.log" removeInRFC="true">
<section title="Since draft-ietf-httpbis-safe-method-w-body-00" anchor="changes.since.00">
Expand Down