Re: X-Content-Type-Options: nosniff

On Fri, Apr 3, 2015 at 7:39 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> Yesterday Chrome dev was still failing several of those for me.

Chrome does appear to still have parsing differences with IE11 by the
way (I treated IE11 as authoritative on header parsing since they
introduced it):

  https://w3c-test.org/fetch/nosniff/parsing-nosniff.html

Perhaps Chrome discards the header altogether when there's several?
IE11 only counts the first.


-- 
https://annevankesteren.nl/

Received on Friday, 3 April 2015 05:54:57 UTC