Is DO Spaces CDN still broken? Any workarounds?

Oh didn’t realize it was a wiki.

I’m a novice with sysadmin/cloud stuff, so hopefully someone can double check me before I make any edits.

These are the missing headers I see in non-CDN /assets but missing in CDN /assets:

  • content-encoding
  • expires (though there’s x-amz-expiration)
  • server
  • X-Firefox-Spdy

When I compare to meta.discourse.org’s cloudfront CDN /assets headers, they’re missing expires (and x-amz-expiration), but have all the other headers compared to non-CDN /assets.

content-encoding seems like the most likely cause of the problem, which lines up with Digitalocean block storage VS amazon S3 - #5 by md-misko.


I also found two open DO community questions, not sure if they’re 100% the same root cause. Hopefully someone can double check me

1 Like