[html5] r2616 - [] (0) When changing encoding on the fly after a POST, don't hit the network aga [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-12-29 15:45:57 -0800 (Mon, 29 Dec 2008)
New Revision: 2616

Modified:
   index
   source
Log:
[] (0) When changing encoding on the fly after a POST, don't hit the network again whatever happens. (bug 6258)

Modified: index
===================================================================
--- index	2008-12-29 23:34:51 UTC (rev 2615)
+++ index	2008-12-29 23:45:57 UTC (rev 2616)
@@ -46833,7 +46833,13 @@
    <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 (<a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or
+   equivalent</a> for non-HTTP URLs), then instead set the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> 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>
 
   </ol><h4 id=parse-state><span class=secno>8.2.3 </span>Parse state</h4>
 

Modified: source
===================================================================
--- source	2008-12-29 23:34:51 UTC (rev 2615)
+++ source	2008-12-29 23:45:57 UTC (rev 2616)
@@ -53418,7 +53418,14 @@
    <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>
 
   </ol>