evanr76

Level 3

Understood.

When you do get around to it, also consider that some CDNs prescribe not just a hostname but as well a full URI for a CDN.

In our situation, our non-SSL CDN hostname is our-company.our-cdn.com/<origin-path>, but our SSL CDN has a prescribed hostname and URI prefix i.e. our-company.secure.our-cdn.com/our-company/<origin-path>

Thanks for making a great plug-in.

Thank you.

Would you consider developing a feature to allow different CDN hosts depending on SSL or non-SSL access?

We looked into Cloudfront, which would work, but the lack of origin pull makes it much less convenient for us.

We have discovered that our existing CDN does support SSL, but the hostname and URI structure is slightly different for SSL.

To be more specific,

When our blog is accessed via SSL, W3TC is trying to rewrite our assets as

https://our-cdn-domain.com/wp-content/&#8230;

but our-cdn-domain.com is not listening on https port so this fails.

@otto42,

Respectfully, it’s one thing if the WordPress development team doesn’t have enough resources to test all possible upgrade scenarios (for example, low memory limit hosted environments), but to say no amount of testing would have uncovered this is simply false.