Question
Compression for JS builds stored in Spaces
- Posted on June 8, 2023
- DigitalOcean Spaces
Asked by Blockmedia Tech
Hi! I’m storing React app builds (js, css and media files) in DO Spaces. Then the build is embedded in other app. Can I enable gzip or other compression in request headers? I noticed that there is such an option in file metadata but for some reason compression headers are still missing in the request
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hi there,
I believe that you might see this behaviour when using the Spaces CDN.
Origin endpoints do not dynamically compress or uncompress content, and they do not modify the content’s
Content-Encodingheader. However, for files downloaded via the CDN, you can set the following metadata headers during upload to the origin to make the CDN dynamically compress or uncompress the file:The CDN endpoints may dynamically compress content, if the origin object does not have
Content-Encoding: gzipand the client sendsAccept-Encoding: gzip. If dynamically compressed, the resulting response has theContent-Encoding: gzipheader added.The CDN endpoints may dynamically uncompress content if the origin object has
Content-Encoding: gzipand the client does not sendAccept-Encoding: gzip. If dynamically uncompressed, the resulting response has theContent-Encoding: gzipheader removed.Hope that this helps!
Best,
Bobby