I'm not sure this is so much a bug, but a possible feature that could be added, so here goes.
I recently encountered a small issue while setting up a site with an SSL certificate. The browsers I tested (firefox, safari, chrome) would give an ssl warning stating that some of the elements on the page may be from non secure sources. I tracked it down to the call to the google fonts api produced by this module.
I changed 'http://' to 'https://' on line 68 of google_fonts_api.module and the warning went away.
I imagine the other modules would exhibit similar behavior, but as I only use the google fonts I did not test.
Perhaps there would be a way to enable an https version of the modules?
Comments
Comment #1
sreynen commentedThis sounds like a bug to me. Thanks for reporting it. I think most, if not all, of the font providers can serve fonts over HTTPS, so it just needs to switch the URLs when the current page is HTTPS.
Comment #2
sreynen commentedThe fix for Google is committed. KERNEST is the only other provider that loads CSS remotely, and they don't yet have that available over HTTPS. I've emailed to ask for that and will open a separate issue if it becomes available.
Comment #3
sreynen commented