Currently Google Chrome (and possibly other browsers too) gives an error about a font that wants loading over HTTP while the website is loaded over HTTPS, causing the font not to be loaded at all (mixed content error).
By loading the font over HTTP always we avoid this problem. We could have loaded the font using the schema-less protocol (//), but that's known to cause problems, so always loading over HTTPS is our best option here.
Currently Google Chrome (and possibly other browsers too) gives an error about a font that wants loading over HTTP while the website is loaded over HTTPS, causing the font not to be loaded at all (mixed content error).
By loading the font over HTTP always we avoid this problem. We could have loaded the font using the schema-less protocol (//), but that's known to cause problems, so always loading over HTTPS is our best option here.