Re: [whatwg/fetch] Define parsing for X-Content-Type-Options in detail (#818) from Anne van Kesteren on 2018-10-30 (public-webapps-github@w3.org from October 2018)

From: Anne van Kesteren <notifications@github.com>
Date: Tue, 30 Oct 2018 05:36:53 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/pull/818/c434283476@github.com>

@MattMenke2 so I updated the tests and ran them again and Chrome and Safari both treat `nosniff` immediately followed by 0x0B or 0x0C as a "valid value". Firefox does so for 0x0C only. I think that's why I went with treating 0x0C as valid and 0x0B as invalid. I'm happy for them to both be restricted, but are you equally sure about wanting this after knowing these results?

-- 
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-434283476

Received on Tuesday, 30 October 2018 12:37:20 UTC