yjhjerry

Hello @vmarko

Thanks for your trouble, really appreciate it.
I disabled AO, removed all files under wp-content/cache/autoptimize/css/, clear Cloudfront cache, now all the static contents can be accessed from CDN.

Now a new problem arises, some icons rendered by font-awesome won’t work. I found out that font-awesome uses the gzip file(awesome.min.css.gzip) with CDN enabled, and it won’t render the icon, But after I disabled CDN, font-awesome uses the normal file(awesome.min.css), this is when icons could be rendered correct again.

The gzip file was generated when I tried uploading theme files to the S3 bucket using WTC. I am not an expert of front-end. but is it could be that after the gzip file was received, somehow the browser failed to unzip it…? Or it could be anything else?

Thanks so much again for the time and trouble…

Best regards,
Jerry

Hi @vmarko

Thanks for the reply.

I believe one of the things that WTC does behind the scenes is overwrite the origin web server hostname with the CDN hostname, so that when the page loads, static assets could be retrieved using the CDN’s hostname. Problem is that I found in the page source quite a few hostname in the static content url is still my website hostname, they are all under wp-content/themes/theme/images, but some are using CDN hostname, some are not…

I wonder why is this.

Best regards,
Jerry