- From: Ruben Verborgh <notifications@github.com>
- Date: Fri, 08 Mar 2019 11:15:10 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 8 March 2019 19:15:32 UTC
Thanks for trying to summarize @sleevi, that's helpful. > 'default opt-out' was moreso that a given 'nu-opt-out' will, by default, also opt-out of any new changes Fair enough. If a server says, "I don't want feature X", then it is indeed also opting out of all future alterations to X. Just like, as a server, when I don't provide content negotiation, I am also opting out of content negotiation changes in the future. That is indeed very much the point. > It seemed that there was some concern that there was an expectation that the current opt-out would provide that level of functionality I will remove the mentions out of enable-cors from point 8, they can indeed be confusing. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/878#issuecomment-471043141
Received on Friday, 8 March 2019 19:15:32 UTC