Continuing CORS Issue

  • cgidds

    (@cgidds)


    5 years, 2 months ago

    I’m using AWS for WordPress (Version 4.2.2) and getting the infamous CORS policy issue:

    Access to font at ‘https://www.bethelatx.com/wp-content/themes/grace-church/css/fontello/font/fontello.woff2?10977599’ from origin ‘https://bethelatx.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

    I’ve added the following to the .htaccess file:

    <FilesMatch “\.(ttf|ttc|otf|eot|woff|woff2|font.css)$”>
    <IfModule mod_headers.c>
    Header add Access-Control-Allow-Origin “*”
    Header set Access-Control-Allow-Origin “*”
    </IfModule>
    </FilesMatch>

    Can you please point me in the right direction as to what’s causing this? I’ll re-enable the acceleration once you’ve confirmed you’re able to troubleshoot it.

    • This topic was modified 5 years, 2 months ago by cgidds.
    • This topic was modified 5 years, 2 months ago by cgidds.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 16 through 23 (of 23 total)
1 2
  • Thread Starter cgidds

    (@cgidds)

    5 years ago

    @luckychingi brilliant! that worked 🙂 Can I suggest you add this to the FAQ in the next release?

    Once I finish getting this rolled out fully, I’ll buy you a coffee too!

    Thread Starter cgidds

    (@cgidds)

    5 years ago

    @luckychingi can you explain how you’re determine what to include in the wildcard exclusions? I’m still getting CORS errors on these 2 pages, but everything I try to include in the wildcard doesn’t solve the issue.

    bethelatx.com
    bethelatx.com/new-sermons

    Plugin Author luckychingi

    (@luckychingi)

    5 years ago

    Hello @cgidds

    The plugin checks for the words entered in the wildcard list against the urls for static assets (scripts, images and files)

    Can you give me some examples of words you have in the wildcard list?

    Thread Starter cgidds

    (@cgidds)

    5 years ago

    You bet!

    The most common one that didn’t work is fontawesome and tried that on the following pages:

    bethelatx.com
    bethelatx.com/recent-messages/sermons/
    bethelatx.com/recent-messages/conferences/

    Plugin Author luckychingi

    (@luckychingi)

    5 years ago

    Could you try to add font-awesome.min.css to the Wildcard exclusion list?

    Thread Starter cgidds

    (@cgidds)

    5 years ago

    @luckychingi that worked! Are you primarily looking at the filename and including that instead? Or is it a case-by-case basis?

    Plugin Author luckychingi

    (@luckychingi)

    5 years ago

    @cgidds

    Not a filename but a keyword that is unique to the stylesheet / JavaScript link

    alexdex

    (@alexdex)

    4 years, 11 months ago

    Hi, I have the same issue, going crazy to fix it
    I already add in the wildcard exclusion font-awesome.min.css
    But no success, idem the htaccess file, I have almost 20 errors
    See here: https://wineandtaste.com/shop/

    Please help me

Viewing 8 replies - 16 through 23 (of 23 total)
1 2

The topic ‘Continuing CORS Issue’ is closed to new replies.