Problems with DigitalOcean Spaces use as CDN
-
Hello,
There were two issues regarding use of DigitalOcean Spaces as an S3-compatible CDN and they issues continue to exist with the current W3TC plugin (0.14.3).
1. https://www.ads-software.com/support/topic/cannot-use-digitalocean-spaces-as-cdn/
2. https://www.ads-software.com/support/topic/gzip-minified-files-not-uploading-to-cdn/The first is that these content-length errors continue to be generated, but the file is successfully uploaded after what appears to be a retry.
Error: Unable to put object (S3Compatible::putObject(): [411] Unexpected HTTP status).
2. I think the errors above might be related to this problem. I have a genuine Amazon S3 bucket into which the plugin did successfully upload the file wp-includes/css/dashicons.min.css.gzip. However the plugin will not upload this same file to the S3-compatible DigitalOcean Spaces bucket, and thus the website is getting 403 errors trying to access all of the minified nonexistent files at DigitalOcean Spaces that the plugin did succeed in uploading to Amazon AWS S3.
PLEASE ask the developers to look again at the ticket you opened in #1 above, and to do a simple side-by-side comparison of the two object storage systems to fix these small but show-stopping bugs. Thank you.
- The topic ‘Problems with DigitalOcean Spaces use as CDN’ is closed to new replies.