Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818)

The only somewhat icky bit here in my opinion is using "isomorphic encode" to avoid the lack of byte sequence manipulation infrastructure. It seems fine for now, but worth keeping an eye on.

I also filed a follow-up, unrelated to that: #817.

cc @MattMenke2

-- 
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/pull/818#issuecomment-430614783

Received on Wednesday, 17 October 2018 12:49:51 UTC