Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-3391

404 errors when retrieving EOT resources in IE



    • Type: Bug
    • Status: Volunteer Needed (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.6, 6.0
    • Fix Version/s: None
    • Component/s: XMLUI
    • Attachments:
    • Comments:
    • Documentation Status:


      This issue may also apply to JSPUI.

      We were investigating the 404 errors in our DSpace instance. We discovered that this issue is also visible on demo.dspace.org.

      My colleague provided the following analysis. Note that the issue is not visible in a Network trace in all browsers. The error appears to manifest in IE.

      The error is triggered in


      When I specifically follow a link to:


      I get a 404 also, so perhaps this is best filed as a bug.

      The actual CSS that is calling the .EOT is:


      { font-family:'Glyphicons Halflings'; src:url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.eot?#iefix) format(embedded-opentype),url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.woff) format(woff),url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.ttf) format(truetype),url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.svg#glyphicons_halflingsregular) format(svg); }

      And I am able to download the other referenced files (.WOFF, .TTF, .SVG) referenced in this declaration. I suspect this file is missing from the distribution.

      Since .EOT files are only compatible with IE, it could be that only IE is triggering the 404s.

      the Glyphicon font is getting called for the Home icon in the breadcrumb and the Magnifying Glass icon on the search button, and there are probably others.

      The .EOT declaration is really only there for IE8 and below, which accounts for only 2% of our traffic. Those users are likely not seeing those icons.

      My understanding is that some browsers start parsing the font-face source URLs from the bottom, then work their way up, while others start at the top and just ignore .EOT references, which is why we might not be seeing the 404s triggered all the time.


      { font-family:'Glyphicons Halflings'; src: url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.eot?#iefix) format(embedded-opentype), url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.woff) format(woff), url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.ttf) format(truetype), url(../vendor/bootstrap-sass-official/assets/fonts/bootstrap/glyphicons-halflings-regular.svg#glyphicons_halflingsregular) format(svg); }

      When I inspect network traffic in IE11's inspector mode, I do see the 404 (see attached screenshot) regardless of whether I'm in Compatibility mode or not, but you can also see that it eventually successfully retrieves the .WOFF file after the 404 is returned on the .EOT.

      When I do the same in Chrome and FF, Chrome retrieves the .WOFF file but not the .EOT and FF doesn't show any font activity (which seems weird).




            terrywbrady Terrence W Brady
            0 Vote for this issue
            1 Start watching this issue