[whatwg/fetch] CORS: consider further restrictions on Content-Type (#790)

Once parsing and serializing of this header is defined in detail, we should consider a parse-and-serialize operation for this header to prevent malicious values being smuggled through MIME type parameters. Perhaps even restrict those parameters to charset and preflight otherwise.

-- 
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/790