Google Fonts API returning multiple URLs that result in 404 errors

[onassar]

A number of fonts (possibly new ones) returned via the Google Fonts API are returning 404 errors when the URL is accessed. Example:

Name: Noto Sans KR
Weight: 100
Version: 6
https://fonts.gstatic.com/s/notosanskr/v6/Pby6FmXiEBPT4ITbgNA5CgmOsn7o.ttf

[sladen]

How is the font actually being requested?

(Please copy and paste the exact code being used to load the font via the Google Fonts API).

[onassar]

Just stepped out the door but if you request it even in your browser you’ll notice you get a 404

On Wed, Sep 5, 2018 at 9:17 AM Paul Sladen ***@***.***> wrote: How is the font actually being requested? (Please copy and paste the exact code being used to load the font via the Google Fonts API). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1679 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlaSi6ndbDDEvX70wFHs1sjE2_2bkvgks5uX87fgaJpZM4Wa35U> .

-- — Oliver Nassar

[sladen]

Yes, but where is the the URL coming from.

What code is being used, that results in the CSS, that references this URL.

[onassar]

I am requesting fonts via this URL:
https://www.googleapis.com/webfonts/v1/webfonts?key={accessKey}&sort=alpha

It returns all fonts, which I then cache on my side to prevent subsequent lookups, and perform text matching.

Here is the exact record match:

Notice that the URL for the 100 style points to this URL:
http://fonts.gstatic.com/s/notosanskr/v6/Pby6FmXiEBPT4ITbgNA5CgmOsn7o.ttf

Which then provides a 404. I also tried changing the protocol to https, but no luck.

[sladen]

What is the contents of the Expires: HTTP header returned with this JSON result?

[onassar]

If I run a curl from CLI, I get this:
expires: Wed, 05 Sep 2018 15:36:00 GMT

Command: curl -i -H -D https://www.googleapis.com/webfonts/v1/webfonts?key={accessKey}&sort=alpha

[sladen]

Invalid URLs being return for all results matching:
*"lastModified": "2018-09-04",

(ie. changed in the last 24 hours). Wonder if something failed preventing successful staging/deployment of the actual TTFs?

Thank you for spotting this!

[onassar]

Yeh of course; I regularly run tests of the endpoints to make sure everything is working properly, so I'll post here again in the future if I run into something similar.

Any idea on an eta for a fix? Happy to test + confirm.

[sladen]

Note to self whilst investigating, 2x Sans in category: Sans-serif:

   "family": "Noto Sans JP",
   "category": "sans-serif",
…
   "family": "Noto Sans KR",
   "category": "sans-serif",

• "Noto Serif JP"
• "Noto Serif

[onassar]

Do you want a list of all the fonts I could reproduce this with?

[sladen]

It appears to be four: `Noto {Sans,Serif} {JP,KR}". Are there others?

[nyshadhr9]

Hello, Thank you for spotting this.
I think this is a bug on our end, breaking the URLs on developer API for:
Noto Sans KR
Noto Sans JP
Noto Serif KR
Noto Serif JP

We are working on a fix; I'll be back with an ETA soon. Sorry for the inconvenience.

[onassar]

Yep that looks right.