Adding options for image CDN, with push capabilities.
-
Hey,
I am currently testing out KeyCDN as a possible switch from Amazon S3 and Cloudfront, mainly due to Amazon slacking on any kind of HTTP/2 support.
However, there is one huge thing that may stop me from doing this (at least partially).
For pull origins, KeyCDN is awesome, it works great and it’s easy to set up, however, there doesn’t seem to be much support for push origins in your plugins, which is a problem for us.
I have already seen that you do not want to add the ability for more domains in the CDN plugin, however, for our set up, it would be nice if you would add the option for an image CDN, as we use two CDN URLs, one for big content like videos and images (Push), and another for JS and CSS (Pull), as you can see they both need different domains.
Alongside that, it would be nice to have an automatic push to a push CDN from the plugin.
Finally, a question does the cache enabler’s WebP function work with the Push CDN?
For now, I think that I am going to setup a KeyCDN pull for my AWS bucket, which should provide all this with HTTP/2 support.
The topic ‘Adding options for image CDN, with push capabilities.’ is closed to new replies.