Hi guys,
I am pretty new to metabase and I am wondering about one aspect (did not find any results on this forum nor on Google):
While using the Metabase-Frontend, I realized calls to “fonts.googleapis.com” and “ajax.googleapis.com”.
My question(s) now:
Can they be disabled somehow?
What would happen, if such calls would not succeed/be blocked?
Thx and best regards,
Tom
Adding some additional background to this: in many data centers (Germans are data security maniacs 
) AJAX calls to the public web are strictly forbidden either on organizational level (you are not allowed to deploy) or enforced via strict CSP security policies.
Fonts could be likely easily embedded and shipped with the application itself, not sure about those ajax.googleapis.com calls though. Any help/input appreciated.
Thanks,
Jan
Hi @Tom_S
That is used for initializing the font-family Lato. If you block it, then the font would fall-back, since very few computers has the font available.
But it’s currently not something you can do with a simple toggle in the settings.
Hi @jza
To avoid duplicates, I’m just going to ask you. Can you create a new issue, which describes reasons for including the fonts and avoiding the two external JS calls?
And please post the link here.
- anyone else, upvote by clicking