Re: [whatwg/xhr] Define Content-Type manipulation in terms of MIME Sniffing (#176)

I'm not sure why it would be. You already have an analogous operation you are using:

> Let value be the value of the header whose name is a byte-case-insensitive match for `Content-Type` in author request headers. 

What's wrong with just defining it that way?

---

As for testing all the MIME types, I was thinking, set Content-Type/the value from the JSON file for every value in the JSON file. Then, check that the resulting Content-Type the server sees is the same as the output from the JSON file, except all charset parameters must be changed to UTF-8 (so do something like `s/charset=[A-Z-]+/charset=UTF-8`).

-- 
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/xhr/pull/176#issuecomment-380189283