Chrome loads the text / html file, but shows the status "failed" and does not display on the screen

Question

There is still a weird issue with Google Chrome. I have a text / html page generated from php source code. This page loads well and displays well in all popular browsers except Chrome. When the source code has just been saved, Chrome downloads and makes the file correct. Even if I just added or removed a space. Then, if I try to refresh the page, Chrome displays a blank page and displays an error message in the Developer Tools pane (see Screenshot) indicating the failure state. But if I check the HTTP response headers, everything will be fine, including the HTTP status: 200 OK.

HTTP/1.1 200 OK Date: Mon, 17 Sep 2012 08:37:03 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.3.14 Expires: Mon, 17 Sep 2012 08:52:03 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 

The following are the headers for HTTP responses immediately after saving the source and getting the correct rendering. No change (except time information)

 HTTP/1.1 200 OK Date: Mon, 17 Sep 2012 08:56:06 GMT Server: Apache/2.2.3 (CentOS) X-Powered-By: PHP/5.3.14 Expires: Mon, 17 Sep 2012 09:11:07 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 

I also checked the headers of the HTTP request, they are the same in both cases:

Working case:

 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4 Cache-Control:max-age=0 Connection:keep-alive Cookie:PHPSESSID=qn01olb0lkgh3qh7tpmjbdbct1 Host:(hidden here, but correct, looks like subsubdomain.subdomain.domain.tld) User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 

Bad case:

 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4 Cache-Control:max-age=0 Connection:keep-alive Cookie:PHPSESSID=qn01olb0lkgh3qh7tpmjbdbct1 Host:(also hidden) User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 

I noticed that even if the page failed, some other resources (javascript, style sheets) are successfully loaded or retrieved from the local cache. I can also access the HTML source code every time whether the page can be displayed or not (HTML code is what is expected to contain).

I also ran Wireshark to see if there would be something wrong with the data transfer or something like that, but on this side everything is fine too.

I read something on Google about the content that will cause Chrome to crash if the information provided in the HTTP headers is different from the effective size of the supplied file. It seems to me that this is not so, since the length of the content is not provided.

Any help would be appreciated! Thanks!

Answer 1

For those still facing the problem: Add setEnv downgrade-1.0 to your .htaccess, this works as a temporary fix for me. It disables the transmission of channels.

Another solution is to install the user agent in IE, apparently it does the same ...

The actual problem is related to the server configuration, I also see segmentation error errors. The site I encounter this behavior runs on PHP 5.3.27 via HTTPS.

edit: It doesn't matter if the site is accessible via HTTPS or HTTP.

edit2: the cause of this error was one extremely long line, dividing it into several lines, solved the problem.