If you have any questions, please write issues, and let me know.

[keshikan]

If you have any questions, please write issues, and let me know.

[mrthnmn]

Keshikan, It turns out the problem is not with your file. I apologize. I thought it was because the error I was getting indicated it was a cross-site access problem which usually means you're trying to load something from an http site into a https site. Sincerely, Bruce Hyatt

…

On Wed, Apr 26, 2017 at 11:30 PM, keshikan ***@***.***> wrote: Hi Bruce, Thank you for informing me. Umm.. is this a problem of DSEG font file itself? or SSL protocol? (or both?) I just added *.woff2 <https://github.com/keshikan/DSEG/releases/tag/v0.42>. I hope this release will solve your problem. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQKaMMxQBdRljIwdkBjMXauwXQhE3ZKoks5r0AvKgaJpZM4MhFIu> .

[mrthnmn]

Hello Keshikan,

I wanted to use your DSEG7 font for a code-camp project I am working on. The problem is, I am hosting the font file on my secure web site and apparently the font file gets the typeface from an unsecure Google site. This appears to be causing a CORS problem - many, if not all browsers now, will not allow secure sites to pull data from unsecure sites.

Do you know of any workarounds, short of editing the font file to route the request through a CORS proxy?

TIA,
Bruce Hyatt

[keshikan]

Hi Bruce,

Sorry, I have no idea about your problem.
I don't know a lot about CORS proxy.

keshikan

[mrthnmn]

I don't mean to suggest work for you but one solution might be to use https instead of http in the src urls (https://fonts.gstatic.com/s/lato/v13/UyBMtLsHKBKXelqf4x7VRQ.woff2). I checked and it appears to link to the same site this way.

Bruce

[mrthnmn]

Keshikan, Because many web sites are moving to encryption (https), many users of your fonts may start having this problem. If you are interested, it may be easy to fix by changing the font-face src urls (http://fonts.gstatic.com...) to https (https://fonts.gstatic.com...). I checked and it appears that the urls work that way. Sincerely, Bruce Hyatt

…

On Wed, Apr 12, 2017 at 8:19 AM, keshikan ***@***.***> wrote: Hi Bruce, Sorry, I have no idea about your problem. I don't know a lot about CORS proxy. keshikan — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQKaMI9VdJT8Kxv8ll7dDsYK3WFoA1D_ks5rvMFrgaJpZM4MhFIu> .

[keshikan]

Hi Bruce,
Thank you for informing me.

Umm.. is this a problem of DSEG font file itself? or SSL protocol? (or both?)

I just added *.woff2. I hope this release will solve your problem.