Access to font blocked by CORS policy

  • Resolved martingfisher

    (@martingfisher)


    4 years, 8 months ago

    When activating the CSS/Js feature I get a number of console errors related to icon based fonts. How can I exclude these. I managed to exclude some errors using your exclusion feature but not these?

    

Access to font at 'https://mlscndeftln6.i.optimole.com/FeWCCEQ--tNnCL4s/f:css/q:75/m:1/https://insuranceforlocalmedia.com/wp-content/themes/salient/css/fonts/icomoon.woff' from origin 'https://insuranceforlocalmedia.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
icomoon.woff:1 Failed to load resource: net::ERR_FAILED
(index):1 Access to font at 'https://mlscndeftln6.i.optimole.com/FeWCCEQ-BI8Fk78-/f:css/q:75/m:1/https://insuranceforlocalmedia.com/wp-content/themes/salient/css/fonts/fontawesome-webfont.woff?v=4.2' from origin 'https://insuranceforlocalmedia.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
fontawesome-webfont.woff:1 Failed to load resource: net::ERR_FAILED
(index):1 Access to font at 'https://mlscndeftln6.i.optimole.com/FeWCCEQ--tNnCL4s/f:css/q:75/m:1/https://insuranceforlocalmedia.com/wp-content/themes/salient/css/fonts/icomoon.ttf' from origin 'https://insuranceforlocalmedia.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
icomoon.ttf:1 Failed to load resource: net::ERR_FAILED
(index):1 Access to font at 'https://mlscndeftln6.i.optimole.com/FeWCCEQ-BI8Fk78-/f:css/q:75/m:1/https://insuranceforlocalmedia.com/wp-content/themes/salient/css/fonts/fontawesome-webfont.ttf?v=4.2' from origin 'https://insuranceforlocalmedia.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
fontawesome-webfont.ttf:1 Failed to load resource: net::ERR_FAILED
    • This topic was modified 4 years, 8 months ago by Yui. Reason: code formatting
    • This topic was modified 4 years, 8 months ago by Yui.
Viewing 4 replies - 1 through 4 (of 4 total)
  • OMP

    (@spiderdudececil)

    Hi there. I’m having the same issue with fonts. Were you able to find a resolution to your problem?

    Hello,

    You can add the following lines inside your .htaccess and it should solve the issue with fonts:

    <FilesMatch “.(eot|otf|ttf|woff|woff2)”>
    Header always set Access-Control-Allow-Origin “*”
    </FilesMatch>

    Also clear the cache if you use any caching plugins, if the issue persists you can contact us directly via https://optimole.com/#contact

    Thank you!

    OMP

    (@spiderdudececil)

    Hi Bogdan. Thanks for following up. I should have clarified thatI’ve already tried the steps mentions in earlier posts (i.e. add the lines you provided to htaccess, deactivating and reactivating the plugin, specifying the problematic file in the exclusion filter, and clearing the caches after each attempt).
    I’m using the Breeze caching plugin with varnish, by the way.

    Hello,

    You can contact us directly https://optimole.com/#contact
    And provide us with a link to your website so we can see what might happen.
    If required I can then send you our support plugin to try solve this.

    Let us know, thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Access to font blocked by CORS policy’ is closed to new replies.