• John

    (@dairehardesty)


    Hi, after setting up the plugin correctly, I still get cors errors on fonts even though I have updated the .htaccess. What am I missing?

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author luckychingi

    (@luckychingi)

    hello @dairehardesty

    Can you share the content of the .htaccess file?

    Thread Starter John

    (@dairehardesty)

    Here it is:

    
    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END WordPress" are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
    ##### Added By AWS CDN Plugin #####
    
    <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>
    
    Plugin Author luckychingi

    (@luckychingi)

    Thanks @dairehardesty

    When testing with the curl command, I get the following output:

    * subjectAltName: host “d2kd4pgiyuktng.cloudfront.net” matched cert’s “*.cloudfront.net”
    * issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
    * SSL certificate verify ok.
    * Using HTTP2, server supports multi-use
    * Connection state changed (HTTP/2 confirmed)
    * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
    * TLSv1.3 (OUT), TLS Unknown, Unknown (23):
    * TLSv1.3 (OUT), TLS Unknown, Unknown (23):
    * TLSv1.3 (OUT), TLS Unknown, Unknown (23):
    * Using Stream ID: 1 (easy handle 0x563e88fc3710)
    * TLSv1.3 (OUT), TLS Unknown, Unknown (23):
    > OPTIONS /wp-content/themes/fluxus/fonts/icomoon.ttf?vadmn3 HTTP/2
    > Host: d2kd4pgiyuktng.cloudfront.net
    > User-Agent: curl/7.58.0
    > Accept: */*
    > Origin: https://dairehardesty.com/
    > Access-Control-Request-Method: POST
    > Access-Control-Request-Headers: X-Requested-With
    >
    * TLSv1.3 (IN), TLS Unknown, Unknown (23):
    * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
    * TLSv1.3 (OUT), TLS Unknown, Unknown (23):
    * TLSv1.3 (IN), TLS Unknown, Unknown (23):
    * TLSv1.3 (IN), TLS Unknown, Unknown (23):
    < HTTP/2 200
    < content-type: font/ttf
    < content-length: 0
    < server: nginx
    < date: Thu, 11 Mar 2021 13:30:56 GMT
    < x-accel-version: 0.01
    < allow: OPTIONS,HEAD,GET,POST
    < access-control-allow-origin: *
    < strict-transport-security: max-age=15768000; includeSubDomains
    < x-powered-by: PleskLin
    < x-cache: Hit from cloudfront
    < via: 1.1 c65a32dc5e5c096e25909838173845c7.cloudfront.net (CloudFront)
    < x-amz-cf-pop: YTO50-C3
    < x-amz-cf-id: IBnlZZqxE4tbNFt5ytcrvI4ZYUPvnz82Um0Jem5K-6Y4q3DInNw3Zg==
    < age: 241`

    The output seems to be correct. Could you clear cache on your website and also purge the cache on AWS Cloudfront?

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cors issue’ is closed to new replies.