- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 3 Feb 2021 09:09:16 +0100
- To: ietf-http-wg@w3.org
Am 03.02.2021 um 03:57 schrieb Martin Thomson: > On Wed, Feb 3, 2021, at 12:37, Mark Nottingham wrote: >> I think the use case is 'I want to convey a well-formed body that >> reflects the error state as best I can, and have the client show it to >> the user, but I changed my mind on the caching policy due to the >> aforementioned error.' > > Why then would this be limited to caching policies? That suggests you might have a different content-type then. More seriously though, this suggests that you are reneging on the status code. > ... Right. While I understand why we might want to avoid touching the status code, this is really what this is about. In particular, an HTTP client that doesn't cache at all (and thus is not interested in Cache-Control in the first place) might want to handle this as well. Best regards, Julian
Received on Wednesday, 3 February 2021 08:09:34 UTC