IIS & Chrome: failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING It also may be as simple as you need to update your Chrome install (as this problem is Chrome specific). You should be able to test this by extending the script execution time. I am not really sure why it should affect only you but it could be down to a bunch of race conditions? That's an utter guess.

In your case, it might be a case of the script timing out. So when the connection is closed, the page is not yet loaded. It is also possible that Chrome (or connection or something) is being slow. On the other hand, it could be that the server does not send the terminal 0-length chunk. In short, a slightly imperfect headers issue. As far as I can tell, it is an issue of these versions being massively sensitive to the content length of the chunk being sent and the expressed size of that chunk (I could be far off on that one). Your issue is trying to figure out why.Īpparently, this might be a known issue impacting a couple of versions of Chrome. The error is trying to say that Chrome was cut off while the page was being sent. Matthew Brown aka Lord Matt 在 21:43:32 回答： If I go into Chrome's settings and use the 'Restore to Default' option, the problem will disappear for about 10-20 minutes. 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. However, forcing HTTP 1.0 over HTTP 1.1 is not a proper solution. While testing, I was able to fix the issue by forcing HTTP 1.0 in my htaccess file: 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.Ĭache-Control:no-store, no-cache, must-revalidate, post-check=0, pre-check=0 I have used Firefox and the exact same thing is occurring.

I have also tried disabling all extensions and browsing in Incognito mode - to no effect. Other people are accessing the exact same server with the exact same version of Chrome. None of our users are experiencing this problem - nor is anybody else on our dev team. It is not happening to anybody else - i.e. This is happening to me on our in-house Apache server. For the past two months, I have been receiving the following error on Chrome's developer console:

Traincraft mod wiki