- From: Ben Schwartz <bemasc@google.com>
- Date: Wed, 3 Feb 2021 16:49:53 -0500
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Wednesday, 3 February 2021 21:50:17 UTC
Restarting on a different tack. On Tue, Feb 2, 2021 at 7:43 PM Mark Nottingham <mnot@mnot.net> wrote: ... > (c) purposefully truncate the response (i.e., cause a protocol error), > hoping that all downstream caches correctly avoid storing incomplete > responses. > Have you encountered caches that don't handle this correctly? This may seem inelegant, but if it works in practice, I think we can codify it into a respectable solution (e.g. forcing a particular kind of protocol error).
Received on Wednesday, 3 February 2021 21:50:17 UTC