title: What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?
body: <p>I'm building a web server and trying to test things.  The server is running on <code>localhost:888</code>, and the first time I load the web app, everything works.  But if I try to reload the page, a bunch of <code>XmlHttpRequest</code> requests fail with <code>net::ERR_FAILED</code>.  By putting breakpoints in the server code, I can verify that the requests are never actually coming in.</p>
  
  <p>This isn't a connection failure, as the connection succeeds the first time.  The fact that it succeeds once and then fails later implies that it might be caching-related, but there's nothing in the server code that sets the <code>cache-control</code> header.  So I tested it by putting the server up on an actual web server.  The first time, everything had to take its time loading; the second time, it all loaded instantly, so this is definitely cache-related</p>
  
  <p>This is a custom server running on top of <code>http.sys</code> (no IIS), and it appears that things are getting cached by default and then failing to load from it on subsequent runs, but only when my server is running on localhost; on the Web, it works fine.  As near as I can tell, <code>net::ERR_FAILED</code> is a generic "something went wrong and we've got no useful information for you" message in Chrome, so I'm kind of stuck here.  Does anyone know what could be causing this?</p>