Is there a poroblem with @fontface on mobile?

Hello @trial_error,

Maybe your mobile browser is still using the old version of the css file. Try to delete the browser cache.
Definitely this is not a plugin-related bug.

Thanks.

Thanks for your swift reply!
I debugged it in Chrome over USB and I think I have caught it now.

When accessing by https://www.example.com it works. But when accessing by example.com the font is prevented from loading. Chrome debug says:

“Font from origin ‘https://www.example.com’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘https://example.com’ is therefore not allowed access.”

I know those http headers exist but have never really been trying to manipulate them. Do you have a suggestion as to how I could proceed? What would I edit, and where?

Thanks a lot for any suggestions.

You can:

1. redirect from https://example.com/ to https://www.example.com. See: https://www.ostraining.com/blog/wordpress/non-www/
2. set “Access-Control-Allow-Origin” header for fonts. See: https://stackoverflow.com/a/5009126/4430200

I would choose the first way.

• This reply was modified 7 years, 11 months ago by George J.
• This reply was modified 7 years, 11 months ago by George J.
• This reply was modified 7 years, 11 months ago by George J.

Excellent! Thanks!!