This is a bit inconsistent, but it allows the DO CDN to be used for S3 uploads only, without breaking the site: It seems that this is by design, because the DISCOURSE_S3_CDN_URL env variable, if set in the app.yml, overrides the CDN setting for assets too, while this same setting, when declared in site settings only, doesn’t? If those parameters are set in the site settings via web admin console, the DO only serves the S3 uploads via CDN, and the site assets are still served from the source. That means you can use their Object Storage offering, but must shop for a caching CDN in another provider.Ī missing content-encoding in the DO CDN implementation definitely is a bummer, but it only happens when setting all the S3 parameters inside app.yml.
Metadata headers are correctly set when fetching content directly from the origin.Ī missing content-encoding means all our brotli encoded assets are broken. Using Object Storage for Uploads (S3 can you share any specifics on this CDN brokenness?ĭue to a known issue, file metadata headers like Content-Encoding are not passed through the CDN.
0 kommentar(er)
