-
|
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 I'm just wondering if this a bug or if this is intended. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
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 For the To troubleshoot this issue, you can check the following:
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 |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @yurishkuro , Apologies. You are correct that it was a problem with the Ingress I was using. It was changing the Sorry about the trouble. |
Beta Was this translation helpful? Give feedback.
Hello @yurishkuro ,
Apologies. You are correct that it was a problem with the Ingress I was using. It was changing the
Content-Typeheader 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.