As you may know, yuo can customize the error pages in Cloudflare, such as for a WAF block, etc.
For some reason, since the switchover to the new error pages dashboard, the custom font I always use isn't working.
I can see that it converted https://cdn.daniweb.com/font.woff into inline base64 for the @font-face CSS, which sounds about right. However, it's not working for whatever reason, and I have no idea why.
Has anyone heard of anything like this before?
I would check out assets you add to custom error page. See https://developers.cloudflare.com/rules/custom-errors/
Hello Dwight,
I had already checked out that link, but from what I can gather, Cloudflare does not consider individual resources (such as fonts, images, etc.) as "assets". My understanding is than an asset is the entire HTML file used to generate the page, complete with inline, base64 encoded resources.
As you may know, yuo can customize the error pages in Cloudflare, such as for a WAF block, etc.
For some reason, since the switchover to the new error pages dashboard, the custom font I always use isn't working.
I can see that it converted https://cdn.daniweb.com/font.woff into inline base64 for the @font-face CSS, which sounds about right. However, it's not working for whatever reason, and I have no idea why.
Has anyone heard of anything like this before?
It sounds like there might be an issue with how Cloudflare is handling the font conversion or loading process; checking the CSS or cache settings might help resolve the issue
Yes, it is. Cache settings are irrelevant? I was really just wondering if anyone else has experienced this issue, and what they did to fix it?
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.
