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

Define request collapsing #480

Merged
merged 4 commits into from
Nov 12, 2020
Merged

Define request collapsing #480

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9f10e84
Define request collapsing
mnot Oct 22, 2020
8c62292
Update draft-ietf-httpbis-cache-latest.xml
mnot Oct 22, 2020
367899c
Merge branch 'master' into mnot-475
reschke Oct 27, 2020
dda11f1
Update draft-ietf-httpbis-cache-latest.xml
mnot Nov 12, 2020
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
10 changes: 10 additions & 0 deletions draft-ietf-httpbis-cache-latest.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -531,6 +531,15 @@
Also, note that unsafe requests might invalidate already-stored responses;
see <xref target="invalidation" />.
</t>
<t>
A response that is stored or storable can be used to satisfy multiple
requests, provided that it is allowed to reuse that response for the requests
mnot marked this conversation as resolved.
Show resolved Hide resolved
in question. This enables caches to "collapse" multiple requests into a single forward
mnot marked this conversation as resolved.
Show resolved Hide resolved
request upon a cache miss, thereby reducing load on the origin server and network.
However, note that if the response returned is not able to be used for some or all
of the collapsed requests, additional latency might be introduced, because they will
need to be forwarded to be satisfied.
</t>
<t>
When more than one suitable response is stored, a cache &MUST; use the
most recent one (as determined by the <x:ref>Date</x:ref> header
Expand Down Expand Up @@ -2491,6 +2500,7 @@
<section title="Since draft-ietf-httpbis-cache-12" anchor="changes.since.12">
<ul x:when-empty="None yet.">
<li>In <xref target="storing.fields"/>, make it clear that only response headers need be stored (<eref target="https://github.com/httpwg/http-core/issues/457"/>)</li>
<li>In <xref target="constructing.responses.from.caches"/>, mention collapsed requests (<eref target="https://github.com/httpwg/http-core/issues/475`"/>)</li>
</ul>
</section>
</section>
Expand Down