Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>**Edit 4/1/10: ** Update: The 4k bug is now fixed by the IE8 Cumulative update on 3/30/2010. blogs.msdn.com/ieinternals/archive/2010/04/01/</p> <p>The Internet Explorer team has been investigating this issue. </p> <p>-=Impact=-</p> <p>Thus far, we believe the problem has no impact on the end-user's experience with the web application; the only negative effect is the spurious/malformed requests sent by the JavaScript speculative-download engine. When the script is actually needed by the parser, it will properly be downloaded and used at that time.</p> <p>-=Circumstances=-</p> <p>The spurious-request appears to occur only in certain timing situations, only when the pre-parser is forced to restart (as when a META HTTP-EQUIV tag containing a Content-Type with a CHARSET directive appears in the document) and only when a JavaScript SRC URL spans the 4096th byte of the HTTP response body.</p> <p>-=Workaround=-</p> <p>We currently believe this issue can generally be mitigated by declaring the CHARSET of the page using the HTTP Content-Type header rather than specifying it within the page.</p> <p>So, rather than putting </p> <p>[META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"]</p> <p>In your head tag, instead, send the following HTTP response header:</p> <p>Content-Type: text/html; charset=utf-8</p> <p>Note that specification of the charset in the HTTP header results in improved performance in all browsers, because the browser's parsers need not restart parsing from the beginning upon encountering the character set declaration. Furthermore, using the HTTP header helps mitigate certain XSS attack vectors.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload