# האם DO Spaces CDN עדיין שבור? יש פתרונות עוקפים?
**URL:** https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094
**Category:** Support
**Created:** [13 באוגוסט, 2022, 4:32am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094 "2022-08-13T04:32:24Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@ipoopfool](https://meta.discourse.org/u/ipoopfool)
#### Post date: [13 באוגוסט, 2022, 4:32am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/1 "2022-08-13T04:32:24Z")
I was trying to set up a Spaces CDN for my Spaces bucket and after some headache regarding the subdirectory path, SSL, and precompile, I got it working, sort of. All the assets load correctly but nothing is executing. Based on [Digitalocean block storage VS amazon S3 - #5 by md-misko](https://meta.discourse.org/t/digitalocean-block-storage-vs-amazon-s3/158290/5), it seems like the `content-encoding` header is stripped, which is breaking things.
Can anyone confirm if this is the source of the problem and that it remains an open bug with DO?
Has anyone found a workaround to this? A free CDN would be a massive cost savings.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [13 באוגוסט, 2022, 4:39am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/2 "2022-08-13T04:39:57Z")
> [@ipoopfool](#):
>
> Can anyone confirm if this is the source of the problem and that it remains an open bug with DO
That’s right. You need to use a different CDN.
> [@Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916/1):
>
> ### Digital Ocean Spaces
>
> DO offering is good and works out of the box. Only problem is that their CDN offering is awfully broken, so you need to use a different CDN for the files.
---
### Author:  [@ipoopfool](https://meta.discourse.org/u/ipoopfool)
#### Post date: [13 באוגוסט, 2022, 4:43am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/3 "2022-08-13T04:43:23Z")
Cool, thank you!
Personally, I think I would love to see additional details in the [Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916/1) post, maybe even a DO open issue, so that I could confirm the issue and that it was still up to date info.
Maybe that’s just the part of me that wants to confirm everything myself 🙂
---
### Author:  [@maiki](https://meta.discourse.org/u/maiki)
#### Post date: [13 באוגוסט, 2022, 5:09am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/4 "2022-08-13T05:09:59Z")
Hiya! 👋
The doc at [Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916) is a wiki. We are collaboratively documenting how various CDNs work. I don’t use DigitalOcean’s object storage, so I can’t provide anymore details. Perhaps you could? 🙂
> [@ipoopfool](#):
>
> maybe even a DO open issue, so that I could confirm the issue and that it was still up to date info.
That’s a great suggestion, I like to provide a link to allow users of a service to lend their voice to prioritize fixes. I did some searching and couldn’t find a specific issue about DO’s CDN, but I found several spread all over the place. 🤔 Which one do we link to? As a user of the service, our community relies on contributors like you to check out those details. 👍
---
### Author:  [@ipoopfool](https://meta.discourse.org/u/ipoopfool)
#### Post date: [13 באוגוסט, 2022, 4:58pm UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/5 "2022-08-13T16:58:57Z")
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](http://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](https://meta.discourse.org/t/digitalocean-block-storage-vs-amazon-s3/158290/5).
* * *
I also found two open DO community questions, not sure if they’re 100% the same root cause. Hopefully someone can double check me
- [How do I enable gzip compression on Spaces? | DigitalOcean](https://www.digitalocean.com/community/questions/how-do-i-enable-gzip-compression-on-spaces)
- [Access-Control-Expose-Headers: How to expose additional headers in spaces CDN? | DigitalOcean](https://www.digitalocean.com/community/questions/access-control-expose-headers-how-to-expose-additional-headers-in-spaces-cdn)
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [13 בספטמבר, 2022, 6:08am UTC](https://meta.discourse.org/t/is-do-spaces-cdn-still-broken-any-workarounds/236094/7 "2022-09-13T06:08:00Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.