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

MattMenke2 commented on this pull request.



> +steps:
+
+<ol>
+ <li><p>Let <var>value</var> be the result of <a for="header list">getting</a>
+ `<a http-header><code>X-Content-Type-Options</code></a>` from <var>list</var>.
+
+ <li><p>If <var>value</var> is null, then return false.
+
+ <li><p>Let <var>stringValue</var> be the <a>isomorphic decode</a> of <var>value</var>.
+
+ <li>
+  <p>Let <var>tokens</var> be the result of
+  <a lt="split on commas">spliting <var>stringValue</var> on commas</a>.
+
+  <p class="note">This intentionally strips U+000C FORM FEED, despite 0x0C not being being a
+  <a>HTTP whitespace byte</a>.

Sorry, hadn't really focused on this.  What's the motivation here?  Historical reasons?  Looks like Chrome manages to not treat this byte as special, at least in the HTTP header parser.  If we don't absolutely need this, I'd rather get rid of it, just from a keeping things consistent standpoint.

-- 
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#pullrequestreview-166582578