title: IE 11 fails to load resource files
body: <p>I have an application employing FontAwesome's glyph fonts for icons, and everything works fine when I host the files from my server.  When I enable CDN support on my site, IE 11 behaves rather strangely in regards to the font files.  When navigating to a page either via clicking a link or manually entering a URL, the font files load fine ~95% of the time.  If I reload a page or use forward/back buttons (or the ~5% of the time a normal page load doesn't work), IE 11 loads the first font file, loses/drops/ignores the contents of the response body somehow, tries to load the second file, loses the contents of the response body, wash-rinse-repeat, and I end up with no font glyphs.  All other browsers (including older versions of IE) work fine.</p>
  
  <p><code>@font-face</code> declaration in CSS:</p>
  
  <pre><code>@font-face {
      font-family: 'FontAwesome';
      src: url('/common/fonts/fontawesome-webfont.eot');
      src: url('/common/fonts/fontawesome-webfont.eot?#iefix') format('embedded-opentype'),
          url('/common/fonts/fontawesome-webfont.woff') format('woff'),
          url('/common/fonts/fontawesome-webfont.ttf') format('truetype'),
          url('/common/fonts/fontawesome-webfont.svg#fontawesomeregular') format('svg');
      font-weight: normal;
      font-style: normal;
  }
  </code></pre>
  
  <p>Normal page load:</p>
  
  <p>Summary:</p>
  
  <pre><code>URL                                     Protocol  Method  Result  Type                      Received  Taken   Initiator   Wait  Start  Request  Response‎‎  Cache read‎‎  Gap‎‎
  /common/fonts/fontawesome-webfont.eot   HTTPS     GET     200     application/octet-stream  99.78 KB  109 ms  @font-face  2449  0      47       62        0           1420
  </code></pre>
  
  <p>Response header:</p>
  
  <pre><code>Key                            Value
  Response                       HTTP/1.1 200 OK
  Content-Type                   application/octet-stream
  Last-Modified                  Mon, 04 Aug 2014 12:49:48 GMT
  Accept-Ranges                  bytes
  ETag                           "07ef492e2afcf1:0"
  Server                         Microsoft-IIS/7.5
  P3P                            CP="NON DSP COR ADM DEV PSA IVA CONi TELi OUR BUS NAV"
  Access-Control-Allow-Origin    *
  Content-Length                 101712
  Expires                        Mon, 15 Sep 2014 18:48:40 GMT
  Cache-Control                  max-age=0, no-cache, no-store
  Pragma                         no-cache
  Date                           Mon, 15 Sep 2014 18:48:40 GMT
  Connection                     keep-alive
  </code></pre>
  
  <p>Response body contains font file.</p>
  
  <p>On page reload:</p>
  
  <p>Summary:</p>
  
  <pre><code>URL                                     Protocol  Method  Result  Type                      Received  Taken  Initiator   Wait  Start  Request  Response‎‎  Cache read‎‎  Gap‎‎
  /common/fonts/fontawesome-webfont.eot   HTTPS     GET     200     application/octet-stream  462 B     47 ms  @font-face  983   0      47       0         0           1248
  /common/fonts/fontawesome-webfont.woff  HTTPS     GET     200     application/x-font-woff   461 B     63 ms  @font-face  1092  0      63       0         0           1123
  /common/fonts/fontawesome-webfont.ttf   HTTPS     GET     200     application/octet-stream  462 B     93 ms  @font-face  1155  15     78       0         0           1030
  </code></pre>
  
  <p>Response header (for "fontawesome-webfont.eot", the others look the same, except for differences in content-length, accounting for the differences in file size):</p>
  
  <pre><code>Key                            Value
  Response                       HTTP/1.1 200 OK
  Content-Type                   application/octet-stream
  Last-Modified                  Mon, 04 Aug 2014 12:49:48 GMT
  Accept-Ranges                  bytes
  ETag                           "07ef492e2afcf1:0"
  Server                         Microsoft-IIS/7.5
  P3P                            CP="NON DSP COR ADM DEV PSA IVA CONi TELi OUR BUS NAV"
  Access-Control-Allow-Origin    *
  Content-Length                 101712
  Expires                        Mon, 15 Sep 2014 19:05:13 GMT
  Cache-Control                  max-age=0, no-cache, no-store
  Pragma                         no-cache
  Date                           Mon, 15 Sep 2014 19:05:13 GMT
  Connection                     keep-alive
  </code></pre>
  
  <p>Response body is empty.  Note that content length in the details does not match the "received" value in the summary.</p>
  
  <p>According to CDN logs and tracking traffic locally in Fiddler2, the full font files are being served up by the CDN.  As near as I can tell, the response from the CDN is identical to the response from my server.</p>
  
  <p>Enabling caching seems to eliminate the effect (at least, I have not been able to reproduce it with caching enabled), but the Powers That Be are concerned that this will affect other, non-cacheable, assets in the application as more are transitioned over to the CDN, and thus I must find the root cause and fix it rather than slap a band-aid on it.</p>
  
  <p>Why might IE 11 behave as if the responses have empty response bodies?  Why might IE 11 treat a response from a CDN differently from a response from the app server, if the files and response headers are the same?  </p>