You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In verison 0.116 it was enough to add "/" to the end of the URL.
e.g. no listen.prefix configured, reverseproxy forwards "https://.../mon/karma" -> "http://<karma-pod/service>/" (strip-prefix)
Working URL in browser was "https://.../mon/karma/"
Now this does not work anymore, because path to assets is not relative but absolute, now.
So assets are always tried to be loaded from /assets/...
Config value listen.prefix only works for the index.html but is ignored for assets.
Additionally setting custom.js or custom.css to any value leads to /assets/custom.css or /assets/custom.js respectively. So this can also not be used as workarround.
This is a major issue in nearly all web frameworks. As I do not understand the one used here, could you please verify if this is an issue in the way you use this framework, or if it is a bug or missing feature in the framework and open an issue there?
The text was updated successfully, but these errors were encountered:
In verison 0.116 it was enough to add "/" to the end of the URL.
e.g. no listen.prefix configured, reverseproxy forwards "https://.../mon/karma" -> "http://<karma-pod/service>/" (strip-prefix)
Working URL in browser was "https://.../mon/karma/"
Now this does not work anymore, because path to assets is not relative but absolute, now.
So assets are always tried to be loaded from /assets/...
Config value listen.prefix only works for the index.html but is ignored for assets.
Additionally setting custom.js or custom.css to any value leads to /assets/custom.css or /assets/custom.js respectively. So this can also not be used as workarround.
This is a major issue in nearly all web frameworks. As I do not understand the one used here, could you please verify if this is an issue in the way you use this framework, or if it is a bug or missing feature in the framework and open an issue there?
The text was updated successfully, but these errors were encountered: