HTML Standard Tracker


File a bug

SVNBugCommentTime (UTC)
2616When changing encoding on the fly after a POST, don't hit the network again whatever happens. (bug 6258)2008-12-29 23:45
@@ -53411,21 +53411,28 @@ interface <dfn>MessageChannel</dfn> {
    <li>Otherwise, <span>navigate</span> to the document again, with
    <span>replacement enabled</span>, and using the same <span>source
    browsing context</span>, but this time skip the <span>encoding
    sniffing algorithm</span> and instead just set the encoding to the
    new encoding and the <span
    title="concept-encoding-confidence">confidence</span> to
    <i>confident</i>. Whenever possible, this should be done without
    actually contacting the network layer (the bytes should be
    re-parsed from memory), even if, e.g., the document is marked as
-   not being cacheable.</li>
+   not being cacheable. If this is not possible and contacting the
+   network layer would involve repeating a request that uses a method
+   other than HTTP GET (<span title="concept-http-equivalent-get">or
+   equivalent</span> for non-HTTP URLs), then instead set the <span
+   title="concept-encoding-confidence">confidence</span> to
+   <i>confident</i> and ignore the new encoding. The resource will be
+   misinterpreted. User agents may notify the user of the situation,
+   to aid in application development.</li>
   <h4>Parse state</h4>
   <h5>The insertion mode</h5>
   <p>The <dfn>insertion mode</dfn> is a flag that controls the primary