fonts.css 404s for some UAs

[ckarlof]

Investigating now, but it may be related to how connect-fonts caches generated fonts.

[ckarlof]

[ckarlof]

Here's the code I suspect: https://github.com/shane-tomlinson/connect-fonts/blob/d4134e35e2e9d8fe82f3a9378ef25f84807dfb78/lib/css-responder.js#L166

connect-fonts generates and caches fonts based on ua, requested fonts, and locale. One way we could get 404s is that that connect-fonts thinks it has a cached font, but there is no matching file on disk.

I suspect a server restart would resolve this, but let's not do that yet.

[vladikoff]

Change the user agent to something "unique" helps generate the font-file

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Firefox/999.0

i.e Firefox 999

[ckarlof]

Yeah, we're removing this magic in train-10, so maybe we just need to get train-10 out. :) I have some questions about our release process for @mostlygeek, though, before we do that.

[ckarlof]

Leaving this open until we can verify it's fixed on train-10 release, but nothing to worry about now. We'll get Helvetica until train-10 goes live and love it.

[pdehaan]

This can be closed after train-10 leaves the station. #choochoo

[zaach]

Train 10 is live. 🚋 🚋 🚋