- From: Ben Schwartz <bemasc@meta.com>
- Date: Thu, 2 Jul 2026 09:31:42 -0400
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: ietf-http-wg@w3.org
On Thu, Jul 2, 2026 at 9:13 AM Julian Reschke <julian.reschke@gmx.de> wrote: > Am 30.06.2026 um 23:49 schrieb Ben Schwartz: ... > > * The server needs to know that the QUERY is likely to be repeated, so > > the response is cached. > > Or a cache... How is this different from GET? Indeed, this aspect is pretty much the same as with GET. One difference from GET is that we imagine the QUERY body may be "large". This makes caching somewhat less attractive, if it requires storing a large QUERY key in addition to the response value. This proposal changes that balance, but only if the cache knows that clients are likely to use this digest-QUERY behavior. --Ben
Received on Thursday, 2 July 2026 13:32:03 UTC