title: Chrome net::ERR_INCOMPLETE_CHUNKED_ENCODING error
body: <p>For the past two months, I have been receiving the following error on Chrome's developer console:</p>
  
  <pre><code>net::ERR_INCOMPLETE_CHUNKED_ENCODING
  </code></pre>
  
  <p>Symptoms:</p>
  
  <ul>
  <li>Pages not loading.</li>
  <li>Truncated CSS and JS files.</li>
  <li>Pages hanging.</li>
  </ul>
  
  <p>Server environment:</p>
  
  <ul>
  <li>Apache 2.2.22</li>
  <li>PHP</li>
  <li>Ubuntu</li>
  </ul>
  
  <p>This is happening to me on our in-house Apache server. It is not happening to anybody else - i.e. <strong>None of our users are experiencing this problem - nor is anybody else on our dev team.</strong></p>
  
  <p>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.</p>
  
  <p>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.</p>
  
  <p>Response Headers from Apache:</p>
  
  <pre><code>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
  </code></pre>
  
  <p>While testing, I was able to fix the issue by forcing HTTP 1.0 in my htaccess file:</p>
  
  <pre><code>SetEnv downgrade-1.0
  </code></pre>
  
  <p>This gets rid of the problem. However, forcing HTTP 1.0 over HTTP 1.1 is not a proper solution.</p>
  
  <p><strong>Update</strong>: 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, <strong><em>the problem will disappear</em></strong> for about 10-20 minutes. Then it returns.</p>