The issue you're encountering with the .woff, .ttf, .woff2, and .eot font files generating an error 500 and being served with a "json" mime type is likely due to the HTTP server (WebSphere) not recognizing these font file formats or their associated mime types.
To resolve this, you can add the correct mime types for these font files to the WebSphere HTTP server. Here's how you can do it:
-
Modify the mime.types configuration: In WebSphere, you can configure mime types for various file formats by modifying the mime.types file or through the WebSphere admin console:
-
WebSphere Admin Console: If you don't want to modify the mime.types file directly, you can add the mime types via the WebSphere Admin Console by navigating to:
- Servers > WebSphere servers > [Your server] > MIME Types.
- Add the necessary mime type entries for the font file extensions.
This should resolve the 500 error and ensure the proper mime types are set for the font files.
If modifying these settings doesn't work or isn't an option, you might consider submitting an RFE (Request for Enhancement) with IBM for more robust handling of web font files within extensions.
------------------------------
Joe Breath
------------------------------