- From: Ben Kelly <notifications@github.com>
- Date: Tue, 10 Mar 2020 17:03:43 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 March 2020 17:03:57 UTC
Also, I thought whatwg was focused on describing what browsers implement instead of theoretical purity. The reality is that browsers have implemented the distinction between content-set headers and browser-set headers when it comes to CORS preflights for a long time. We ran into a lot of compat pain when we tried to remove the distinction in order to conform strictly to the current spec text. -- 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/1005#issuecomment-597200587
Received on Tuesday, 10 March 2020 17:03:57 UTC