- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 9 Jul 2025 21:28:10 +0200
- To: Roy Fielding <fielding@gbiv.com>
- Cc: ietf-http-wg@w3.org
> On 9 Jul 2025, at 9:09 pm, Roy T. Fielding <fielding@gbiv.com> wrote: > > Deploying body-scanners just to handle QUERY is doomed because the existing pipelines don’t work that way, on purpose. Yes, we could change our own origin code just for this extension, but it won’t work consistently for chained requests via multiple CDNs. We have zero desire for unchained traffic. > > I don’t expect to be right about this stuff all the time. A deployment might prove me wrong. CDNs already do this, because there's significant demand for it. E.g., https://techdocs.akamai.com/property-mgr/docs/cache-post-responses https://developers.cloudflare.com/workers/examples/cache-post-request/ ... and of course the various use cases that caused consideration of QUERY in the first place (e.g., Elasticsearch) tend to have their own caching infrastructures, which shows interest in the capability. Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 9 July 2025 19:28:16 UTC