csbwebmaster

That would be great.

I do like how easy you made the plugin. It is almost perfect for my needs. SOme of the others add such a level of overhead and complexity or do not really support AWS Cloudfront as anything but an ancillary CDN. I get that CLOUDFLARE is probably more popular today. BUt I don’t use it for many very important reasons.

I appreciate what you are doing and know what it’s like to give your time and effort. I thank you.

If you do take this up in a future release, that would be great. Perhaps the plugin should have a configuration option to additionally rewrite relative URLS for selected assets available via the CDN.

(I wonder also if you could have a box where users can select what TYPES they want to come from the CDN. JPG, TIFF, ICO, PDF, PNG, and others. Might give the flexibility to decide what assets can be redirected through the CDN.

(we do have some PDFs or other doc types that we make available regularly).

Anyways, not suggesting that you incorporate these ideas. Just putting them forward. I know they would take quite a bit of time to code, test, release, support.

??

Thanks for the response. I think I’ll hard code them for now. At least the bigger images that I want to have come from the CDN. (We have a lot of high-rez background images that take a lot to pull from our HOST. My organization likes them. it’s just that it puts a load on our host server to serve them).

??

No worries on the delay, Lucky It’s not unexpected to be patient!

??

All of the images are in the uploads folder.

Let me see if I understand you.

What it appears is that the logic you are using in the plugin requires ABSOLUTE URL references (beginning in our case with ‘https://christianservicebrigade.ca/…’ in order to be rewritten. And that relative URL references are not rewritten. is that right?

The DIVI theme, when using a background image picker, puts relative URLS in place (like many themes / plugins do) to local media sources.

I don’t know that I can globally tell DIVI or WordPress to hardcode all URLS to absolute.

SO i’m not sure what to do.

SO I did a little testing. the Plugin is clearly copying images to the CloudFront CDN. IN the case of regular image tags, images are generally being pulled from the CDN.

However, background images and items refered to in CSS are not. I can obviously hardcode the URLs in the CSS to pull from the CDN. BUt this hardcoding seems really unwise.

Is there a needed setting so that relatively linked CSS page content source img urls are prepended with the CDN URN?

I would think localsite image references in a site’s CSS would commonly need to be dynamically have their URN changed so that they pull from the CDN.

(PS. We are using DIVI as our theme. I can manually use hardcoded image references in most of the theme designer editor components. I’d just not prefer to hardcode them by hand).

Just seems like I’m missing some basic capability in the Amazon AWS CDN plugin. PRobably something I didnt do in setting it up corretly.

Thank you. I’ve been working hard to get it optimized.

We are a very tiny non-profit and usually get little web traffic. Recently, we had an event where 400 near simultaneous users attempted to access the site to sign up for registration (a WPFORM). I was surprised to see that the hosting provider (AWS lightsail) couldn’t handle it. So I’ve been doing everything possible to optimize, including implementing our first CDN.

Thanks for the reply, BTW. I really don’t do a lot of WP for scale…mostly small sites. But I used to be a Director doing enterprise infrastructure, and designing for scalability was my thing back then.

I’ve a few things to figure out yet with Cloudfront/W3TC: Does purge trigger a purge of Cloudfront or just the Apache servers (W3TC/WP) cache?

Is there a way to add versioning to file names or assets with a plugin so that updated assets published are newly populated to Cloudfront? (We use BigCommerce. When files are uploaded into their media library, they all get an asset link with a version that helps ensure refreshed assets are used.

How do I ensure old/unused assets are dropped out of cloudfront or doesn’t that matter?

How can I ensure that Cloudfront helps RE: DDOS and other threats.

I was going to look into Cloudflare, but chose not to for quite a few reasons that I won’t get into here. But besides my main requirement (scalability, asset caching), is protection. I’ve not yet figured that out with CLoudfront.

These are some things I’m still working on. I’m also trying to do some load testing using jmeter (I don’t have access to LoadRunner) to test the newly CDN-optimized site for scale. I’m sure we won’t really get much in the way of traffic anytime soon. But I’m hoping the recent reconfiguration, use of W3TC/Cloudfront, gives me a bit more scale. I don’t know how AWS Lightsail can be boosted (if at all) given load/demand. I don’t know that it’s fixed or scalable as a service.

Anyways, thanks for the reply. Got some more to do yet. But it’s improving.

Just a quick note, I figured out partly that it was the W3TC minify feature that was causing my layouts to be pooched (including missing images).

Turned that off and instead used a different minification plug in and at least my site is back to normal in terms of visibility and proper display now.

Phew!

Ok, I have worse problem now none of my images are coming from the CDN.

I feel so over my head on this one. Going to turn off w3tc