Disallowed MIME type error in Jaeger UI

[Red-GV]

Hello,

I'm trying to run the latest v2 (2.5.0) on Kubernetes behind an Ingress. I was able to run the UI behind a custom path using the base-path feature of jaeger-query. However, when accessing the service via the browser, all I'm seeing is a white screen. When I look at the logs, I noticed that the JavaScript and CSS files in the static directory have this error:

JavaScript - was blocked because of a disallowed MIME type (“text/html”)
CSS - was not loaded because its MIME type, “text/html”, is not “text/css”

I'm just wondering if this a bug or if this is intended.

[dosubot[bot]]

Hello @Red-GV! I'm here to help you tackle bugs, answer your questions, and assist with becoming a contributor. While you wait for a human maintainer, feel free to share more details about your issue, and I'll do my best to assist you!

The issue you're encountering with disallowed MIME types for JavaScript and CSS files in Jaeger UI is likely related to how the Content-Type headers are being set when these static files are served. The base-path feature in jaeger-query is used to set the base path for all HTTP routes, which is helpful when running Jaeger behind a reverse proxy ^[1].

For the index.html file, Jaeger UI sets the Content-Type header to "text/html; charset=utf-8" ^[2]. However, for other static files, the http.FileServer is used, which should automatically set the appropriate Content-Type based on the file extension. If the MIME type is incorrectly set to "text/html" for JavaScript and CSS files, it might be due to misconfiguration or an issue with how the files are being served through the Ingress.

To troubleshoot this issue, you can check the following:

1. Ingress Configuration: Ensure that your Ingress configuration correctly routes requests to the Jaeger service and does not alter the Content-Type headers for static files.

2. Reverse Proxy Settings: Verify that any reverse proxy settings are not interfering with the MIME type headers.

3. Jaeger Configuration: Double-check the Jaeger configuration to ensure that the base-path is correctly set and that there are no additional settings affecting the serving of static files.

If the issue persists, it might be worth checking for any updates or patches related to this version of Jaeger UI that address MIME type handling.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yurishkuro]

However, when accessing the service via the browser, all I'm seeing is a white screen.

This doesn't mean it's an issue with Jaeger. When you run standalone Jaeger all the MIME types it returns are sensible, e.g.:

If you're having issues with Istio setup you should probably test Jaeger first without Istio, e.g. by using kubectl port-forward

[Red-GV]

Hello @yurishkuro ,

Apologies. You are correct that it was a problem with the Ingress I was using. It was changing the Content-Type header to constantly be wrong type when rewriting the url. I'm not entirely sure why it did that. However, it is not a problem for this repository.

Sorry about the trouble.