Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions fetch.bs
Original file line number Diff line number Diff line change
Expand Up @@ -3491,6 +3491,30 @@ Content-Type:
</table>
</div>

<p>To <dfn export>legacy extract an encoding</dfn> given failure or a <a for=/>MIME type</a>
<var>mimeType</var> and an <a for=/>encoding</a> <var>encoding</var>, run these steps:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

encoding -> fallbackEncoding would be a big improvement IMO.


<ol>
<li><p>If <var>mimeType</var> is failure, then return <var>encoding</var>.

<li><p>If <var>mimeType</var>["<code>charset</code>"] does not <a for=map>exist</a>, then return
<var>encoding</var>.

<li><p>Let <var>tentativeEncoding</var> be the result of <a for=/>getting an encoding</a> from
<var>mimeType</var>["<code>charset</code>"].

<li><p>If <var>tentativeEncoding</var> is failure, then return <var>encoding</var>.

<li><p>Return <var>tentativeEncoding</var>.
</ol>

<div class=note>
<p>This algorithm allows <var>mimeType</var> to be failure so it can be more easily combined with
<a>extract a MIME type</a>.

<p>It is denoted as legacy as modern formats are to exclusively use <a for=/>UTF-8</a>.
</div>


<h3 id=x-content-type-options-header>`<code>X-Content-Type-Options</code>` header</h3>

Expand Down