- From: Alex Rousskov <rousskov@measurement-factory.com>
- Date: Mon, 10 Sep 2018 10:21:05 -0600
- To: ietf-http-wg@w3.org
On 09/10/2018 03:24 AM, Alessandro Ghedini wrote: > Also agree that the "ERROR" cache-action seems redundant given that we already > have ways to signal errors with status codes. The client receives only one status code. While working on the client request, the proxy may encounter _and_ work around both internal and external errors, responding with 200 (OK). Today, such encounters and workarounds are sometimes reflected in super-actions like MISS_REFRESH_FAIL_OLD. It would be much better to list them as individual (failed) actions with individual error details. Alex.
Received on Tuesday, 11 September 2018 06:33:59 UTC