You are viewing an historical archive of past issues. Please
report new issues to the appropriate project issue tracker on
GitHub.
Comments
-
Greg Hurrell
It's not due to CORS, as I've set up the appropriate headers; eg. the Firefox console shows:
GET https://d3ogqji57fkqg9.cloudfront.net/assets/fontawesome-webfont-4de7b126797e5a5646cc026394183a99.woff
And the response headers (pasted directly from Firefox) are:
X-Cache: Miss from cloudfront X-Amz-Cf-Id: GoJJmblNor9JPEuUO3BvWdFNJwwNAOO5hghjKoAkQoyPlFChgRRA4A== Via: 1.1 3cc911e7eb2df956e3f7c8f27c198a0b.cloudfront.net (CloudFront) Server: nginx Expires: Sat, 11 Apr 2015 07:20:58 GMT Date: Fri, 11 Apr 2014 07:20:58 GMT Content-Type: application/octet-stream Content-Length: 44432 Connection: keep-alive Cache-Control: max-age=31536000, public Access-Control-Allow-Origin: wincent.dev Accept-Ranges: bytes
Nevertheless, the console claims:
downloadable font: no supported format found (font-family: "FontAwesome" style:normal weight:normal stretch:normal src index:4) source: (end of source list)
Other fonts (ie. from Google) work fine; eg:
GET https://themes.googleusercontent.com/static/fonts/inconsolata/v7/BjAYBlHtW3CJxDcjzrnZCLrIa-7acMAeDBVuclsi6Gc.woff
FontAwesome font loads fine in Safari and Chrome.
-
Greg Hurrell
Status changed:
- From: new
- To: closed
Add a comment
Comments are now closed for this issue.