镀铬网:: ERR_INCOMPLETE_CHUNKED_ENCODING错误 [英] Chrome net::ERR_INCOMPLETE_CHUNKED_ENCODING error
问题描述
在过去的两个月里，我已经收到Chrome的开发者控制台上显示以下错误：
For the past two months, I have been receiving the following error on Chrome's developer console:
net::ERR_INCOMPLETE_CHUNKED_ENCODING
症状：
- 无法载入网页。
- 截断CSS和JS文件。
- 网页挂。
Server环境：
- 的Apache 2.2.22
- PHP
- 的Ubuntu
这是发生在我公司内部的Apache服务器上。这不是发生在任何人 - 即我们的用户没有遇到此问题 - 也不是任何人对我们的开发团队
This is happening to me on our in-house Apache server. It is not happening to anybody else - i.e. None of our users are experiencing this problem - nor is anybody else on our dev team.
其他人访问使用完全相同的Chrome版本完全相同的服务器。我也曾尝试禁用所有的扩展，并在隐身模式下浏览 - 没有效果。
Other people are accessing the exact same server with the exact same version of Chrome. I have also tried disabling all extensions and browsing in Incognito mode - to no effect.
我已经使用Firefox和同样的事情正在发生。截断文件和诸如此类的东西。唯一的一点是，所以你需要检查通过Firebug的HTTP请求，看问题Firefox不会引发任何控制台错误。
I have used Firefox and the exact same thing is occurring. Truncated files and whatnot. The only thing is, Firefox doesn't raise any console errors so you need to inspect the HTTP request via Firebug to see the problem.
来自Apache的响应头：
Response Headers from Apache:
Cache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection:close
Content-Encoding:gzip
Content-Type:text/html; charset=utf-8
Date:Mon, 27 Apr 2015 10:52:52 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Pragma:no-cache
Server:Apache/2.2.22 (Ubuntu)
Transfer-Encoding:chunked
Vary:Accept-Encoding
X-Powered-By:PHP/5.3.10-1ubuntu3.8
测试时，我能够通过强制HTTP 1.0在我的htaccess文件来解决该问题：
While testing, I was able to fix the issue by forcing HTTP 1.0 in my htaccess file:
SetEnv downgrade-1.0
这摆脱了这个问题。然而，迫使HTTP 1.0比HTTP 1.1并不是一个妥善的解决办法。
This gets rid of the problem. However, forcing HTTP 1.0 over HTTP 1.1 is not a proper solution.
更新：因为我是唯一一个遇到此问题，我想我需要花更多的时间研究它是否是一个客户端的问题。如果我进入Chrome的设置，并使用恢复默认设置选项， 问题就会消失的约10-20分钟。然后返回。
Update: Because I'm the only one experiencing this issue, I figured that I needed to spend more time investigating whether or not it was a client side issue. If I go into Chrome's settings and use the "Restore to Default" option, the problem will disappear for about 10-20 minutes. Then it returns.
推荐答案
确定。我经过三重检验这一点，我的 100％确定，这是由我的防病毒（ESET NOD32防病毒软件5）引起的。
OK. I've triple-tested this and I am 100% sure that it is being caused by my anti-virus (ESET NOD32 ANTIVIRUS 5).
每当我禁用实时保护，这个问题就会消失。今天，我离开了实时保护关闭6-7小时，从未发生过的问题。
Whenever I disable the Real-Time protection, the issue disappears. Today, I left the Real-Time protection off for 6-7 hours and the issue never occurred.
几分钟前，我换回来的，只为一分钟内表面的问题。
A few moments ago, I switched it back on, only for the problem to surface within a minute.
在过去24小时的过程中，我已经切换的实时保护，然后再次关闭，只是要确定。每一次 - 结果一直在同一个
Over the course of the last 24 hours, I have switched the Real-Time protection on and off again, just to be sure. Each time - the result has been the same.
更新：我所遇到的另一个开发谁在他的卡巴斯基反病毒软件的实时保护有完全相同的问题。他禁用它，问题就走开了。即似乎这个问题并不限于ESET。
Update: I have come across another developer who had the exact same problem with the Real-Time protection on his Kaspersky anti-virus. He disabled it and the problem went away. i.e. This issue doesn't seem to be limited to ESET.
这篇关于镀铬网:: ERR_INCOMPLETE_CHUNKED_ENCODING错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
