由网友(南鸢北筏)分享简介：我有一盏灯栈几乎没有额外的配置比我的根的.htaccess FallbackResource的index.php present I have a website on a lamp stack with little to no extra configuration other than FallbackRe...

我有一盏灯栈几乎没有额外的配置比我的根的.htaccess FallbackResource的index.php present

I have a website on a lamp stack with little to no extra configuration other than FallbackResource /index.php present in my root .htaccess

当我在Chrome加载根页（本地）我收到

When I load the root page (localhost ) in Chrome I receive

GET http://192.168.163.171/网:: ERR_INCOMPLETE_CHUNKED_ENCODING VM110：1

在约10秒后铬控制台。如果我试图跟在VM110链接：1。它需要我给我的内联JavaScript的顶部

in the chrome console after about 10 seconds. If I attempt to follow the link at VM110:1 it takes me to the top of my inline Javascript.

在这种情况不会发生在任何其他页面，但根 有没有404的访问日志，也没有任何其他异常codeS 有没有错误出现在Apache的错误日志。 的错误不会发生在IE或Firefox的最新版本。 这引起了我的两个当地环境和托管的问题。后者绝对没有配置的变化，我希望成为一个近乎默认的安装。 当我删除 FallbackResource 指令我的网页加载罚款没有错误 This does NOT occur on any other page but root There are no 404's in the access log nor any other abnormal codes There are no errors appearing in the apache error log. The error does not occur in the latest version of IE or Firefox. It caused a problem in both my local environment and hosted. The latter has absolutely no config changes and I expect to be a near default install. When I remove the FallbackResource directive my page loads fine without the error

在index.php文件的根被视为比其他任何网页没什么不同。

In index.php the root is treated no different than any other page.

这都将是一个不是问题的问题，因为一切正确加载，但$ javascript的依赖已完成页面加载从工作p $ pvents。

This would all be a non-issue because everything loads properly BUT it prevents javascript relying on a finished page load from working.

这是什么原因造成的问题，或者新的东西，我可以尝试任何进一步的想法？我考虑过搬到只使用mod_rewrite但是这是非常简单的。

Any further ideas on what is causing the problem or new things I can try? I've considered moving to just using mod_rewrite but this is much simpler.

推荐答案

终于找到了答案，而工作在另一个网站：

Finally found the answer while working on another site:

在 FallbackResource 指令一定要添加一个的DirectoryIndex 指令使用同一个文件。还没有时间去研究为什么，但它固定我的问题。我责备它在Chrome浏览器的bug或者可能是铬超级挑剔的，因为没有其他主要浏览器有问题。

Before FallbackResource directive be sure to add a DirectoryIndex directive with the same file. Haven't had time to research why but it fixed my issue. I blame it on a Chrome bug or possibly Chrome being super picky because no other major browser has an issue.