robin69

it got solved after doing process purge cache from cloudfront panel and force http to https.

Yes it got solved!

This is htaceess file

<IfModule mod_rewrite.c>
######################
## Handling Options for the CORS
     RewriteCond %{REQUEST_METHOD} OPTIONS
     RewriteRule ^(.*)$ $1 [L,R=204]

###################
## Add custom headers

    Header set X-Content-Type-Options "nosniff"
    Header set X-XSS-Protection "1; mode=block"
       # Always set these headers for CORS.
    Header always set Access-Control-Max-Age 1728000
    Header always set Access-Control-Allow-Origin: "*"
    Header always set Access-Control-Allow-Methods: "GET,POST,OPTIONS,DELETE,PUT"
    Header always set Access-Control-Allow-Headers: "DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,C$
    Header always set Access-Control-Allow-Credentials true
</IfModule>

this is my vhost file code

context / {
  location                $DOC_ROOT/
  allowBrowse             1
  extraHeaders            Access-Control-Allow-Origin *

  rewrite  {
RewriteFile .htaccess
  }
  addDefaultCharset       off

  phpIniOverride  {

  }
}

https://cyclecartel.com/

Check widget title of bestsellers and Pannier Backpacks

still not working

https://prnt.sc/vysbr3

screenshot link

I am using litespeed not nginx

@luckychingi any update on this sir?

This can be useful https://forums.aws.amazon.com/thread.jspa?threadID=165257

you are trying to share some resource that is hosted on your origin server. E.g
myserver.com/styles/fonts/some_font.woff

For this you have a distribution in cloudfront and now accessing your file with:
my_distribution_id.cloudfront.net/styles/fonts/some_font.woff

But now it is not allowed to be loaded by origin other than cloudfront.net.

To allow your specific origin, you need to check that ‘Access-Control-Allow-Origin’ header is present in both paths and valid. You need to send this header from your origin server: when you access resource myserver.com/styles/fonts/some_font.woff you should see the header in browser console. In this case cloudfront will cache the header and send it to your visitors as well. If this header is absent, cloudfront will send response without it as well. Note that if you change headers in the origin server you will need to invalidate distribution to propagate your changes in headers.

I got above solution on aws forum. Could you please explain what it means and what i have to do?

i did that sir but it’s not working.
CDN even breaking internal wordpress dashboard icons
https://prnt.sc/v64zar

How to purge cache on cloudfronnt cdn?

Sorry