Closed GoogleCodeExporter closed 8 years ago
Hmm that WOFF url works for me... do you still see this?
Original comment by dcrossland@google.com
on 3 Jan 2012 at 10:21
Yeah. I just tried to load
https://themes.googleusercontent.com/static/fonts/oswald/v2/-g5pDUSRgvxvOl5u-a_W
Hw.woff and it failed to connect.
Original comment by ric...@gmail.com
on 3 Jan 2012 at 10:26
I think we need more details about your browser setup, ideally including either
a network trace of the request/response or screenshot of the headers
sent/received. Is it possible you have a proxy or ad blocker in place that
could be blocking the request? It certainly loads for me and for a majority of
our users.
Original comment by r...@google.com
on 19 Mar 2012 at 7:06
Problem still exists. https://themes.googleusercontent.com/static/fonts/... any
web font loaded under HTTPS does not load successfully. Apart from using HTTP
is there any other solution or workaround?
Original comment by chandras...@amiindia.co.in
on 3 Sep 2012 at 8:24
As said above it appears to be a proxy problem. Works on different network.
Original comment by chandr...@gmail.com
on 3 Sep 2012 at 7:31
[deleted comment]
Review: It is stated that it is a "proxy" problem that somehow blocks IE 8 and
9 from loading HTTPS Google Oswald fonts and that one should "work on a
different" network. This is not good enough for me. Please let us work together
to finding a work-about !!
- The obvious way is to load the font via FTP but I can not find (yet) how to
do this - or if we can do this with Google Fonts. Ideas ....
Frankly I think the issue is NOT about proxy networks but about IE security
settings that one checks to 'Do not save encrypted pages to disk'.
Original comment by ardan.mi...@gmail.com
on 4 Jan 2013 at 11:07
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
I'm interested in clarifying this because I am having the same issue. When I
change the http in the goggle supplied api link for the fonts to https: The net
console in Firebug shows the get operation for the files at
themes.googleusercontet.com as aborted. This also happens in Chrome. Stragely,
the fonts still seem to display; but I can;t shake the feeling that all is not
OK and I'm going to pay the price for this later.
Original comment by clark.mo...@gmail.com
on 12 Feb 2013 at 9:19
Instead of using a protocol in your URL, like
http://fonts.googleapis.com/css?family=Oswald
or
https://fonts.googleapis.com/css?family=Oswald
You can simply use
//fonts.googleapis.com/css?family=Oswald
and this should work more reliably.
Original comment by d.crossland
on 12 Feb 2013 at 9:22
use the javascript method. it worked for me.
Original comment by tokidoki...@gmail.com
on 8 Aug 2013 at 6:04
Thanks for the tip, d.crossland.
Original comment by jjtheb...@gmail.com
on 15 Aug 2013 at 3:36
@d.crossland you're the man! Thanks.
Original comment by juancho....@gmail.com
on 20 Sep 2013 at 1:16
@d.crossland thanks man.. :)
d problem solved instantly..
Original comment by ab.kote...@gmail.com
on 10 Nov 2013 at 8:16
[deleted comment]
Original comment by dcrossland@google.com
on 5 Dec 2013 at 4:18
Thanks a lot d.crossland!!!
Original comment by jcsotose...@gmail.com
on 18 Dec 2013 at 10:50
For my website, I used the javascript method.
Perfect !
Original comment by jamal...@gmail.com
on 19 Jul 2014 at 8:29
@d.crossland you're the man! Thanks.
Original comment by lav...@gmail.com
on 8 Sep 2014 at 8:29
@d.crossland thumbs up!
Original comment by latourl...@gmail.com
on 24 Nov 2014 at 2:07
Original issue reported on code.google.com by
ric...@gmail.com
on 3 Jan 2012 at 8:58Attachments: