A
Alois Treindl
Guest
We observe the same problem.
IE8 browsers loading pages from our server sometimes make requests to in-page resource files (.js, .css etc) with damaged filenames.
We have been able to verify that often 4096 bytes are dropped in the source code, ie. if in the html source it said
the request on our server my look like
/h/menSOMETHING
where SOMETHING is a html fragment from the same page, further down by 4096 bytes. We have also seen case where the distance is different from 4096 bytes.
It seems that some code triggers a bug in IE 8.8 which destroys the internal representation of the list of required resources for that page.
The cause does not have to be in the loaded page itself. We have traced the issue for several days, and found that it is possible that a previously loaded page damages the internal state of IE8, so that it produces the symptoms on a page it gets later.
The case is rare, we have a few hundred bad requests per day in the apache server log, while we serve about half a million pages to IE8 client browsers. IE8 makes about 25% of the user agents we see.
Andreas Pfanner wrote:
IE 8 Parsing issues?
28-Jan-10
Hello,
since a few month we are having strange requests in our web server logs.
Example:
2010-01-27 18:00:35 W3SVC183691552 194.183.128.104 GET
/SysRes/GLOBALSkin/Ski/head>
IE8 browsers loading pages from our server sometimes make requests to in-page resource files (.js, .css etc) with damaged filenames.
We have been able to verify that often 4096 bytes are dropped in the source code, ie. if in the html source it said
the request on our server my look like
/h/menSOMETHING
where SOMETHING is a html fragment from the same page, further down by 4096 bytes. We have also seen case where the distance is different from 4096 bytes.
It seems that some code triggers a bug in IE 8.8 which destroys the internal representation of the list of required resources for that page.
The cause does not have to be in the loaded page itself. We have traced the issue for several days, and found that it is possible that a previously loaded page damages the internal state of IE8, so that it produces the symptoms on a page it gets later.
The case is rare, we have a few hundred bad requests per day in the apache server log, while we serve about half a million pages to IE8 client browsers. IE8 makes about 25% of the user agents we see.
Andreas Pfanner wrote:
IE 8 Parsing issues?
28-Jan-10
Hello,
since a few month we are having strange requests in our web server logs.
Example:
2010-01-27 18:00:35 W3SVC183691552 194.183.128.104 GET
/SysRes/GLOBALSkin/Ski/head>