Since Stack Exchange sites are moving towards HTTPS I was wondering why some pages still use http and not https or // for the Google fonts links or if this is just something that's been missed? For example the 10m page.
-
That page is not such a good example because it'll be gone long before SSL is fully supported.– user259867Commented Aug 28, 2015 at 5:34
-
SSL when loading fonts would slow down the loading speed with unnecessary encryption. It's not needed.– jyoonProCommented Aug 28, 2015 at 6:05
-
2@jyoon wouldn't you get a "mixed content" warning if you loaded them over HTTP though?– ChrisF ModCommented Aug 29, 2015 at 19:37
Add a comment
|
1 Answer
Since Stack Exchange sites are moving towards HTTPS I was wondering why some pages still use http and not https or // for the Google fonts links or if this is just something that's been missed?
Because HTTPS support is still a work in progress. We're upgrading parts of the code as we go along. For example, user avatars are served over HTTPS now.
We should use protocol-relative URLs more, I agree, but in practice it doesn't particularly matter for one-off temporary things like the 10m page considering that we don't fully support HTTPS yet.
answered Aug 29, 2015 at 20:48
-
Yeah I know I just thought sites like google fonts could be moved over sitewide considering there's a https version for it so using https or protocol-relative URLs wouldn't affect anything and would fix pages like that. Commented Aug 30, 2015 at 4:32
-
1@XO All the assets we use will eventually use the appropriate protocol. That's (part of) the plan. :) Commented Aug 30, 2015 at 4:42