I and a few others would very much like to use a popular caching plugin for WordPress (W3TC) to use DigitalOcean Spaces as an automatically updated CDN. It nearly works with the plugin’s S3-compatible configuration, except Spaces produces HTTP status code 411 apparently because of missing Content-Length headers. Other S3-compatible object storage providers somehow manage to carry on without these missing Content-Length headers but Spaces remains unusable (see https://github.com/W3EDGE/w3-total-cache/issues/243).

I am hoping DigitalOcean has some developer resource that can expand the usability for Spaces where customers would otherwise be forced to use other S3-compatible object storage, and write and marshal through a pull request to the plugin to fix this long-standing issue. The fix is definitely not as simple as adding a line of code to include the missing Content-Length header, as a cURL library is making some choices as well, and some very old PHP S3-compatible library is used, but I’m sure it’s not rocket science either.

Thanks for any investigation to broaden the reach of Spaces for users like me.