Hi all,
I wanted to report this in bugtracker, but couldn't log in. The bugtracker acknowledged my account, but didn't allow me to submit a new bug.
The past few days I've been hunting down a bug that caused xmlhttprequests to go nuts in google Chrome, since my last browser update to be more precise (6.0.472.53). The error report in the console's always the same: "Failed to load resource". Works fine in FF and IE.
So I spent an evening tracing the client javascript for pitfalls. I did actually find a bug in my xhr library but halas, no reward.
Just a few moments ago I
did find the cause: the function output($xml) in IXR_Library.php contains:
$length = strlen($xml);
...
header('Content-Length: '.$length);
The problem is that a lot of servers these days compress the output, but apparently don't modify the content-length:
Response Header with content-length in IXR_library
Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection:close
Content-Encoding:gzip
Content-Length:3709
Content-Type:text/xml
Date:Tue, 07 Sep 2010 13:16:59 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Pragma:no-cache
Server:Apache mod_fcgid/2.3.5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Vary:Accept-Encoding
X-Powered-By:PHP/5.2.14
Result: chrome doesn't return responseXML or responseText
Response Header without content-length in IXR_library
Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection:close
Content-Encoding:gzip
Content-Length:513
Content-Type:text/xml
Date:Tue, 07 Sep 2010 13:09:10 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Pragma:no-cache
Server:Apache mod_fcgid/2.3.5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Vary:Accept-Encoding
X-Powered-By:PHP/5.2.14
Result: all is well
I think this is the right place to post this: it's not a Chrome bug, not an IXR-bug, not a DW-bug, but something to think about when configuring the server.