Re: [whatwg/fetch] Proposal: CORS means TAO by default (Issue #1414)

I think CORS can/should imply TAO for resource-level information around timing and size, but my comment in that previous thread still feels relevant:

> I think we also questioned whether TAO can be reasonably interpreted as giving you access to network-level data. That still seems strange to me, given that it reveals data about conditions well beyond a given server's control.

CORS can't enable that (and, IMO, neither should TAO), as it isn't under the server's control, nor is it philosophically within the server's power to reveal. As Anne noted in that thread, this is a more fundamental concern about the access TAO provides.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1414#issuecomment-1070732126
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1414/1070732126@github.com>

Received on Thursday, 17 March 2022 10:07:03 UTC