Closed mdavis-xyz closed 5 years ago
There are a couple things here.
First, the issue you're seeing there is because you're blocking the requests to the charmstore for the icons in the browser. You'll have to whitelist https://api.jujucharms.com/*
for those requests to be allowed out and then shown.
As far as serving the assets from the controller. There is an unfortunate limitation of Juju and modern browsers. Juju only supports loading protected assets (in this case icons) from the controller using u/p in the url. Using a u/p in sub resource requests has been blocked by modern browsers because it can be a potential security issue. We aren't able to resolve this issue on our side, it's dependent on Juju providing some other type of authentication mechanism to fetch these assets.
Juju issue: https://bugs.launchpad.net/juju/+bug/1824887
Ah yes, I see now. It is indeed because of one of my browser extensions. (Privacy Badger.)
The console log messages happen to look like CORS errors, but that's not actually the case.
I have no idea what u/p is.
sorry u/p is shorthand for "user & password"
When I look at the graph in the GUI, I see no icons for charms from the Juju store. Charms which were deployed from local files do have icons.
When I open the browser console I see that this is because of CORS errors.
I'm using Firefox 66.0.2.
One solution is for the SVGs to be served via the Juju controller, which fetches them from api.jujucharms.com, rather than fetching them directly from the browser.