- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 2 Feb 2017 10:23:18 +0900
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 2 February 2017 at 10:12, Mark Nottingham <mnot@mnot.net> wrote: > I don't buy the argument that removal itself adds complexity. Implementations already need to remember what origins they received a 421 for, so they already have the concept of origin set removal. Well, you just established why it might be unnecessary. The gain here is in the client not sending a request to the wrong place. But if this is rare enough, then that cost is probably bearable. The "everything except those" case doesn't concern me that much. I know it's relatively common, but it is fairly rare that the set of origins that are used is not easily enumerable, or incrementally discoverable.
Received on Thursday, 2 February 2017 01:23:51 UTC