CDN SET difference URL for SSL , W3 Total Cache

Please submit a feature request for this case. There are lots of cases that can be supported for CDN in general.

Hi Frederick,
Not sure if it’s the right place to submit a feature request here.
In CDN setting of W3TC, it’s now like
————————————————————–
Replace site’s hostname with: ____.cloudfront.net or CNAME: 1.____
[Add CNAME]

—————————————————————
I suggest to change to

————————————————————–
For SSL:
Replace site’s hostname with: ____.cloudfront.net [submit]

For none SSL, Replace site’s hostname with: CNAME: ____[Add CNAME]
————————————————————–
And change the program logic according to it.

Or keep the old config UI, but in the frontend program, when the page URL is none SSL, all page element will link with CNAME.

If the page URL is SSL, then all page element will be linked with xxx.cloudfront.net.

I too would like to see this functionality implemented. I am using Amazon CloudFront with a couple of CNAMEs, and when the site is accessed via SSL (https), any content that is not loaded from the X.cloudfront.net domain name will not be loaded automatically by the browser.

I completely agree. Right now it is not possible using SSL with W3 Cache + Amazon CloudFront. We need a solution to this.

Many Thanks,
Houman

That feature is in the roadmap.

I’ve been trying to tackle this issue, and looking through the code (and testing) leads me to believe that this feature already exists.

Putting two URLs in the CNAME box, separated by a comma, produces the desired result. When the site is accessed via HTTP, the first URL is used. When the site is accessed with HTTPS, the second URL is used.

Is this the correct functionality? It appears to exactly solve the problem as described.

Also, you really should be charging for this! I greatly appreciate that you actively support it on the forums, but I’d be more than happy to pay for more development.

Clap! Clap!! Clap!!! You worth the picture in your logo.
Unfortunately, I don’t use cloudfront.net function for now, and use cloudflare.com instead.

It’s good to know, but can’t pay you; because I might forget your solution tomorrow if I don’t use it.