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/…
but our-cdn-domain.com is not listening on https port so this fails.
In the development release you can use: DONOTCDN constant in any logic you have, aside from that currently no unless you have a CDN that supports https (like AWS).
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.
It is already in the roadmap. There are just too many possible implementations to prioritize it for now. The plugin already has many options.
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.
Can you advise as to which CDN provider uses such a scheme please?
Have a link to the product you’re using there?
